Wireshark-dev: Re: [Wireshark-dev] Using ptvcursor in a Plugin
: "DeRosa, Anthony" <Anthony.DeRosa@xxxxxxx
: Wed, 23 Jul 2008 14:39:19 -0400
Great, thanks Guy for making the changes to the main branch.
The reason I was a little confused is because I thought my plugin.dll
was linking against a static library (libwireshark.lib). So my
reasoning was that my plugin should work with any release, even those
that didn't export the API, because my plugin was linking against a
*static* library. I now realize that the plugin links against the
libwireshark DLL (the linker uses the libwireshark.lib to locate symbols
that are exported in libwireshark DLL). Like I said, I am not a Windows
developer, but that's what I'm set up to use for now.
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Guy Harris
Sent: Wednesday, July 23, 2008 2:29 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Using ptvcursor in a Plugin
On Jul 23, 2008, at 11:00 AM, DeRosa, Anthony wrote:
> Further clarification...my plugin that uses the ptvcursor API *does*
> successfully load when using the wireshark.exe that I built, after
> having added the ptvcursor API to libwireshark.def. However, when I
> drop my plugin.dll file into a standard installation of wireshark (not
> built from source), the plugin does not load.
> Can anyone further clarify what is going on?
If your plugin uses the ptvcursor routines, and they aren't being
exported by the libwireshark in the standard Wireshark installation,
then your plugin can't be loaded by the standard Wireshark
installation; it can only be loaded by a version of Wireshark that
One way to get an installation of Wireshark that exports the ptvcursor
routines would be to download one of the top-of-tree ("1.0.99")
I've also added the change that exported those routines in the main
branch to the list of fixes to propagate to the 1.0 branch, so if it's
put into a 1.0.3 release, that release will also export the ptvcursor
Wireshark-dev mailing list
This e-mail and any files transmitted with it may be proprietary and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the sender.
Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of ITT Corporation. The recipient should check this e-mail and any attachments for the presence of viruses. ITT accepts no liability for any damage caused by any virus transmitted by this e-mail.