On 9/21/2011 5:05 PM, Guy Harris wrote:
On Sep 21, 2011, at 1:59 PM, Guy Harris wrote:
As for "full integration with Wireshark", they appear to use Wireshark's dissectors in the packet view - they
have a collection of Wireshark DLLs in the "wireshark" subdirectory, along with a bunch of the DLLs we use,
including some GPLed ones. They also have "wireshark.exe", so they might have done the usual "arm's
length" trick to avoid having to give their stuff away.
...but if I try to launch it, it doesn't do anything - pops up a console window
briefly if you double-click it. They also have what I suspect are a pile of
wxWidgets libraries.
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.)
depends: a SysInternals tool from Microsoft.
http://technet.microsoft.com/en-us/library/cc738370%28WS.10%29.aspx
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <[email protected]>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:[email protected]?subject=unsubscribe
