GetModuleHandleA in top Stack-Frame

Hello everybody,

can someone tell me where the “GetModuleHandleA” Method seems to be the entry function of so many Threads (at least the Process Main-Threads)? According to the doc, GetModuleHandleA doesn’t seem to be any kind of entry point.

It there only something going wrong with the Debugger (Symbols, no standard stack-frames)? I think it must be something like this.

Can anybody enlight me in this case?

GP


powered by Exchange 2007 - hosted by a Microsoft Gold Partner - visit us www.world-direct.at

> can someone tell me where the “GetModuleHandleA” Method seems to be the entry function

of so many Threads (at least the Process Main-Threads)?

IIRC, Win32 app main thread’s entry point is a stub in kernel32…dll - this stub calls WinMain(). Once it is not exported, apparently, the debugger presents it’s address like ‘some_ exported_symbol +offset’.
Is it ‘GetModuleHandleA+offset’ string that you see in a debugger???

Anton Bassov

> IIRC, Win32 app main thread’s entry point is a stub in kernel32…dll - this stub calls WinMain().

kernel32!BaseProcessStart calls the EXE’s entry point called like _WinMainCRTStartup, which in turn calls WinMain.


Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com