DLL Entry points

[William W. Plummer]

Is there a program around that will look at a DLL and list its entry points?
Thanks.

 

[David H. Lipman]

Depends.exe from the NT Resource Kit.

In addition:
If you post to UseNet with your TRUE, not a munged, email address then you have invited the
swen Internet worm [aka; W32/Gibe-F] to visit you.

The Swen is news spelled backwards. The reason it is called this is because the Swen worm
harvests email addresses from UseNet News Groups. It has an engine that allows it to post
itself to UseNet News Groups and well as it has its own email engine. From the list of
email addresses that it has harvested, it will then email itself to those addresses.

Dave



| Is there a program around that will look at a DLL and list its entry points?
| Thanks.
|
|

 

[Eric McG]

There is an MS tool called Dependancy Walker which does this:

---quote---
Dependency Walker (Depends.exe)
This tool scans any 32-bit or 64-bit Windows module (including .exe, ..dll, .ocx, and .sys, among others) 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, computer type, debug information, and more.
---END QUOTE---

If this is what you're looking for, this tool is part of the Windows 2000 Support Tools which can be installed from the Windows CD support\tools folder. It is not recommended to extract files from the cab files.

 

[William W. Plummer]

I found Depends in my Vitural Studio stuff. It's display is very
interesting but not quite what I was hoping for. Some services are
started by something like RUNDLL32 SVCHOST.DLL,function . I thought the
function was just an entry in the DLL, and I'm interested in a list of all
the stunts you can SVCHOST and friends do. Can you suggest something else?
Thanks.

There is an MS tool called Dependancy Walker which does this:

---quote---
Dependency Walker (Depends.exe)
This tool scans any 32-bit or 64-bit Windows module (including .exe, .dll,
..ocx, and .sys, among others) 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, computer type, debug
information, and more.
---END QUOTE---

If this is what you're looking for, this tool is part of the Windows 2000
Support Tools which can be installed from the Windows CD support\tools
folder. It is not recommended to extract files from the cab files.

--
Hope this helps..Reply in newsgroup only.
Eric McGillicudy

"William W. Plummer" wrote in message
news:EAlOb.89168$8H.133023@attbi_s03...

 

[Eric McG]

Sorry, but I won't even pretend to know any more about that.

I came across this tool (Depends.exe) and found it useful in troubleshooting a particular problem. It surfaced the case of the infamous missing APPHELP.DLL being called due to a recent update of IE 6....with no solution for Windows 2000 Pro (this file can only exist in WinXP and Win2003 Server).