[Gisle Vanem <gvanem@xxxxxxxxxxxx>]

"Guy Harris" <guy@xxxxxxxxxxxx> wrote:

> Is there an MSVC tool to look find out what DLLs an executable uses?  
> (I.e., the equivalent of, say, ldd on many systems using ELF, or otool on Mac OS X.)

cygcheck from the CygWin package. Running it on AthTek's version of wireshark
reveals this.

G:\internet\sniffer\AthTek-NetWalk\wireshark>cygcheck wireshark.exe
Found: ./\wireshark.exe
./\wireshark.exe
 .\libglib-2.0-0.dll
   f:\windows\system32\ADVAPI32.DLL
     f:\windows\system32\KERNEL32.dll
       f:\windows\system32\ntdll.dll
     f:\windows\system32\RPCRT4.dll
       f:\windows\system32\Secur32.dll
   f:\windows\system32\msvcrt.dll
   f:\windows\system32\OLE32.dll
     f:\windows\system32\GDI32.dll
       f:\windows\system32\USER32.dll
   f:\windows\system32\SHELL32.DLL
     f:\windows\system32\SHLWAPI.dll
   f:\windows\system32\WS2_32.DLL
     f:\windows\system32\WS2HELP.dll
 .\libgthread-2.0-0.dll
 .\libwireshark.dll
   .\libgmodule-2.0-0.dll
   .\libcares-2.dll
   .\zlib1.dll
     .\MSVCR90.dll
   .\libgcrypt-11.dll
     .\libgpg-error-0.dll
   .\libgnutls-26.dll
     .\libtasn1-3.dll
   .\smi.dll
   .\libwsutil.dll
   .\krb5_32.dll
     .\comerr32.dll
       .\k5sprt32.dll
   .\lua5.1.dll
   .\wiretap-0.3.1.dll
 .\MSVCP90.dll

But I failed to get AthTek to work; it didn't capture a single byte on any interface
I tried it on.

--gv