Re: Path of dll's caller
On Sun, 22 Feb 2009 21:27:35 -0500, Joseph M. Newcomer
<newcomer@flounder.com> wrote:
On the whole, you cannot to this easily. You would have to identify the caller by
determining the return address, then correlate that return address with a range of values
that represent code segements of a module, and locate the module from that. There are
some debug-support APIs that exist that can use symbol table information to try to return
a description of the calling module at the address specified, but if you don't have the
right symbol tables, they won't work. You can also do a lot of low-level groveling around
in the bits. Not simple, and probably not particularly reliable.
I once wrote a function to determine if a static object is in the EXE, and
I think a similar approach could be used here. The function was this:
bool
IsStaticObjectInExe(const void* const pObj)
{
// The initial part of a Windows executable is mapped directly into
// its HMODULE, so look at the PE headers to determine the extent
// of the module, which includes its code and static duration data.
const char* const base = (char*) GetModuleHandle(0);
const IMAGE_DOS_HEADER* const pDOS = (IMAGE_DOS_HEADER*) base;
const IMAGE_NT_HEADERS* const pNT = (IMAGE_NT_HEADERS*)
(base+pDOS->e_lfanew);
const char* const end = base+pNT->OptionalHeader.SizeOfImage;
return base <= pObj && pObj < end;
}
I believe the comment applies equally well to DLLs. If so, you would
enumerate the modules using PSAPI (NT4) or ToolHelp (everything else) and
rewrite this function to be "GetModuleFromAddress". The function would take
an HMODULE parameter "base" (instead of calling GetModuleHandle), the
"pObj" parameter would be renamed "pAddress", and the function would return
the containing HMODULE or NULL.
--
Doug Harrison
Visual C++ MVP