Wireshark-dev: Re: [Wireshark-dev] my dissector breaks with updated 1.6 source and libs
From: Alex Lindberg <[email protected]>
Date: Sat, 9 Jul 2011 14:02:48 -0700 (PDT)
I have had much the same issue.

In my case I had to move from the pcre library for regex to the glib way of doing things.  In addition wiretap/file*c have added an additional variable to the function calls to pass error codes and the GTK version of the windows code is moved to its own directory.

BTW, the pcre to glib was necessary because the pcre library is no longer supported for windows compiles (although still referenced in config.nmake).

Alex Lindberg

--- On Fri, 7/8/11, Chris Maynard <[email protected]> wrote:

From: Chris Maynard <[email protected]>
Subject: Re: [Wireshark-dev] my dissector breaks with updated 1.6 source and libs
To: [email protected]
Date: Friday, July 8, 2011, 8:58 PM

Brian Oleksa <[email protected]> writes:

> I have updated to the latest sources today as well as the latest libs.
> I put my dissector in place and it crashes. It ran just fine on 1.4.X

So you previously built a plugin dissector against 1.4.x and dropped it into the
1.6.0 plugins directory expecting it to work?  This has never been supported
because we have yet to lock down the API/ABI, but even if we did, there's no
reason to expect a 1.4 plugin to work against 1.6.  I don't think we'd ever go
so far as to guarantee binary compatibility across anything other than micro
versions.  You will simply have to recompile your plugin against the 1.6 sources
if you intend to use it with 1.6.x.

> What are the major changes...??

Read the release notes for the major changes.

> WHY is this always a problem. Where can I get help with fixing my
> problems..??

Why?  Because Wireshark continues to evolve.

Where can you get help?  -wireshark-devel, ask.wireshark.org, README.developer,
the Wireshark source code, your colleagues, someone you pay for help, etc.
Basically, the usual places.


___________________________________________________________________________
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