Wireshark-dev: Re: [Wireshark-dev] Conference room before FOSDEM
From: Martin Kaiser <[email protected]>
Date: Sun, 29 Jan 2012 19:40:02 +0100
Dear all,

Thus wrote Graham Bloice ([email protected]):

> As the FOSDEM Friday beer event, http://fosdem.org/2012/beerevent takes
> place at Delirium I'm not intending to miss it.

that's for sure, we have to be there and see how many of the 2000
different beers are actually in stock ;-)

To keep us busy until the beer event starts, I've made a list of
of things I'd like to discuss

- opt_comment read patch
   https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3096

   is the general idea behind this ok for you? what can I do to brush up
   the gtk-parts (tooltip etc)?

   I played with writing support as well, I'd appreciate a chat about
   the approach.

- file format plugin

   For my daily job, I worked on a plugin for a (company-internal) file
   format. After some trial and error, it works ok.

   My impression is that there's plenty of documentation and examples
   for dissector and tap plugins, but very little for file format
   plugins.

   Should we improve the documentation and provide a framework and
   sample code? Do we need something like tools/make-dissector-reg for
   file format plugins?

- is it possible to define ASN.1 objects that are used only inside a
  certain dissector and are invisible to the rest of wireshark?

- crash when packets are re-dissected after display filter or
  preference change

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5284  or
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6031
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6172

  this is the wireshark bug I've seen most often. I have the impression
  that it's easy to trigger from my DVB-CI dissector. I'd like to
  understand what I can do to help resolving it.


I look forward to meeting you,

   Martin