Re: dlsym discussion..

["Robert Collins" <robert dot collins at itdomain dot com dot au>]

----- Original Message -----
From: "Andy Moreton" <amoreton@virata.com>
>
> > -----Original Message-----
>
> Looking at this from the Win32 side of things, perhaps you should look
at
> the ToolHelp library, in particular CreateToolHelp32Snapshot(),
> Module32First(),
> and Module32Next().
>
> This will give you a list of all modules for the current process.
Checking
> the
> module handle against the list maintained by cygwin should give the
> information
> you need.
>
> HTH,
>
> AndyM
>

Neato. That combined with before/after dlopen will also let me grab the
dependant libraries that are automatically loaded as well. That won't be
fool proof, but it's better than nothing. I suppose we could fall back
to walking the entire list anyway, but that would likely return
erroneous results :-[

You wouldn't happen to know of an equivalent function for NT 4.0 would
you? (MSND lists that function as win95+, Windows 2000+.

Rob