Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 11687] plugin_if: plugin_if_goto_frame not changing packet

Date: Tue, 10 Nov 2015 13:57:23 +0000

changed bug 11687


What Removed Added
CC   [email protected]

Comment # 1 on bug 11687 from
I tried to reproduce this, using the latest source from git. With my software I
cannot reproduce this on Linux or Windows.

In your Youtube video - btw, the idea is pretty neat, my guess is you will need
this for some kind of automated testing? - it works pretty much my code does,
except the fact, that I exit my plugin after calling and I am calling from a
different thread already.

So basically, I have written a plugin, which implements tap interfaces for
openSAFETY and generates statistics for that specific protocol. The plugin has
it's own gui and is being called using the ext_menubar methods, so it already
runs in a different thread than wireshark does. From there it also generates
it's own GUI context and from there it calls the plugin_if function.

So, one of the things I could recommend would be test, if the thread your
utility is running from, can be more "thread-separated" from the rest of
Wireshark.

Also, how do you start your plugin? Directly with loading wireshark, or do you
need to run a specific dissector first?


You are receiving this mail because:
  • You are watching all bug changes.