Re: [Wireshark-dev] GUI/feature plugins

-Ursprungligt meddelande- Från: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] För RUOFF LARS Skickat: den 22 september 2009 17:10 Till: Developer support list for Wireshark Ämne: [Wireshark-dev] GUI/feature plugins Hi, are there other types of plugins

[Wireshark-dev] GUI/feature plugins

Hi, are there other types of plugins than dissector and tap? Especially, is it possible to write a plugin on Windows (.dll) that extends the Wireshark GUI with additional functionality? README.plugins seems to be about dissector plugins only and stats_tree (the only default tap plugin) doesn't

Re: [Wireshark-dev] gtk_tree_view_column_set_fixed_width: assertion`fixed_width 0

Hi, I checked in a potential fix in revision 30077 if that does not work We need to know what long_str is. Regards Anders -Ursprungligt meddelande- Från: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] För Stephen Fisher Skickat: den 21 september 2009

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-x86

The Buildbot has detected a new failure of OSX-10.5-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-x86/builds/278 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason:

[Wireshark-dev] buildbot failure in Wireshark (development) on Ubuntu-7.10-x86-64

The Buildbot has detected a new failure of Ubuntu-7.10-x86-64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-7.10-x86-64/builds/74 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-7.10-x86

Re: [Wireshark-dev] Lua post-dissector not getting field values

I've been digging into the wslua code, and the wireshark dissection source as well, trying to figure out why perfectly a good header field in wireshark is not getting read by my Lua script's field extractors. Here is what I have figured out so far (some of this will be known to most of you):

Re: [Wireshark-dev] [Wireshark-commits] rev 30076: /trunk/ /trunk/tools/: fuzz-test.sh /trunk/: tshark.c

On Sep 22, 2009, at 9:13 PM, Joerg Mayer wrote: How about making -P a numbered option like -P1 and -P2 and then add a -P1 option to wireshark as well, What would a -P1 option do in Wireshark? ___ Sent via: