--- Lloyd Dupont <lloyd@...> wrote: > i want to know on which
library depend a given dll.
> i use objdump -x but this give me a very big output i have to
> browse, but i only output like foo.dll, bar.dll
Here is a very useful tool by Steve Miller, called Dependency Walker,
that can be used in GUI or console mode. It even allow profiling of
calls with explicit (ie LoadLibrary/GetProcAddress) linkages:
Here is blurb:
Dependency Walker is a free utility that scans any 32-bit or 64-bit
Windows module (exe, dll, ocx, sys, etc.) and builds a hierarchical
tree diagram of all dependent modules. For each module found, it lists
all the functions that are exported by that module, and which of those
functions are actually being called by other modules. Another view
displays the minimum set of required files, along with detailed
information about each file including a full path to the file, base
address, version numbers, machine type, debug information, and more.
(;~/ I wish it were open-source so I could put in G++ name-demangling
http://messenger.yahoo.com.au - Yahoo! Messenger
- Voice chat, mail alerts, stock quotes and favourite news and lots more!