[Wireshark-dev] 0.99.5 - 1.0.0

Hi guys Ages ago I wrote a dissector for Wireshark 0.99.5, which worked fine. I've just tried using Wireshark 1.0.0 and with the same trace I get a malformed packet on the decode! Has anyone else had this problem? Cheers This email and any files attached are intended for the addressee an

Re: [Wireshark-dev] 0.99.5 - 1.0.0

Hi, See http://wiki.wireshark.org/KnownBugs which says "Plugins are not portable between versions". See the porting guide in doc/README.plugins and make any necessary changes, then just recompile. Thanx, Jaap > Hi guys > > > > Ages ago I wrote a dissector for Wireshark 0.99.5, which worked fine.

Re: [Wireshark-dev] 0.99.5 - 1.0.0

Andrew, On Thursday 26 June 2008 09:51, [EMAIL PROTECTED] wrote: > Ages ago I wrote a dissector for Wireshark 0.99.5, which worked fine. > I've just tried using Wireshark 1.0.0 and with the same trace I get a > malformed packet on the decode! Has anyone else had this problem? I had the same probl

Re: [Wireshark-dev] 0.99.5 - 1.0.0

I'm not getting any debug info in Wireshark itself, but if I look into it I'll keep your comments in mind. Thanks. The link Jaap pointed me at sounds like the most likely cause. So I guess I'll either need to update my dev version to 1.0.0 or stick with 0.99.5. Cheers Guys -Original Messag

[Wireshark-dev] need help by "dissector add"

Hello everyone, I need help to create a dissector. I have searched suited informations in the developer's guide and README.developer, but didn't find something. I want to build a dissector, who starts when I have a Profinet Real-Time package with frame id = 0x. At the moment, the package loo

Re: [Wireshark-dev] need help by "dissector add"

Hi !! How about adding this line this line pn_rt_handle = find_dissector("pn_rt); > void proto_reg_handoff_pb(void)> {> static gboolean initialized=FALSE;> > if > (!initialized) { pn_rt_handle = find_dissector("pn_rt); > pb_handle = create_dissector_handle(dissect_pb, proto_pb);> > diss

[Wireshark-dev] (no subject)

Hello, I'm finishing my ged125 dissector and figured I'd check if my name was mentioned in the authors section. It's not. I do have the authors file with my name and email in it. Is there any thing else that I forget to edit/add to my dissector folder? Thanks, martin ___

Re: [Wireshark-dev] [Wireshark-commits] rev 25612: /trunk/epan/dissectors/ /trunk/epan/dissectors/: packet-syslog.c

On Thu, Jun 26, 2008 at 08:40:33PM +, [EMAIL PROTECTED] wrote: > From me: Check if that will happen and chop off the nibble before giving it > to > convert_string_to_hex() so we'll dissect as much of the MSU as possible. Wouldn't it be more helpful to add a 0, that way no information would

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-XP-x86

The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/4501 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-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/45 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-7.10-x86 Build