How to get imagebase after a DLL gets loaded

From: "Jack" <jl@xxxxxxxxxx>
Date: Thu, 30 Nov 2006 16:04:21 +0800

I am wondering whether I should use
MapViewofFile to get the imagebase of a DLL
after loading that module using LoadLibrary? or maybe CreateProcess
It seems to me like a "static-loading" and "dynamic-loading" problem.
If I load it from hard drive, I would need to use MapViewofFile, otherwise I
should use LoadLibrary
or CreateProcess????
Thanks

.

Follow-Ups:
- Re: How to get imagebase after a DLL gets loaded
  - From: Jack
- Re: How to get imagebase after a DLL gets loaded
  - From: William DePalo [MVP VC++]
- Re: How to get imagebase after a DLL gets loaded
  - From: Vladimir Scherbina
- Re: How to get imagebase after a DLL gets loaded
  - From: anton bassov
- Re: How to get imagebase after a DLL gets loaded
  - From: James Brown

Prev by Date: Re: Intro to writing kernel hooks
Next by Date: Re: How to get imagebase after a DLL gets loaded
Previous by thread: Intro to writing kernel hooks
Next by thread: Re: How to get imagebase after a DLL gets loaded
Index(es):
- Date
- Thread

Relevant Pages

Re: How to get imagebase after a DLL gets loaded
... after loading that module using LoadLibrary? ... or maybe CreateProcess ... If I load it from hard drive, I would need to use MapViewofFile, otherwise I should use LoadLibrary ...
(microsoft.public.win32.programmer.kernel)
Re: How to get imagebase after a DLL gets loaded
... MapViewofFile to get the imagebase of a DLL ... after loading that module using LoadLibrary? ... or maybe CreateProcess ... If I load it from hard drive, I would need to use MapViewofFile, otherwise ...
(microsoft.public.win32.programmer.kernel)
Re: How to get imagebase after a DLL gets loaded
... you can also use LoadLibraryEx() - it can ... load a library into your address space without calling its entry point ... MapViewofFile() for the section, opened with SEC_IMAGE flag. ...
(microsoft.public.win32.programmer.kernel)