> -Original Message-
> From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-
> boun...@wireshark.org] On Behalf Of Guy Harris
> Sent: Sunday, October 02, 2011 3:31 PM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] [Wireshark-commits] rev 39143:
> /trun
shjoon OoO wrote:
Hi all
anyone knows what does this error message mean:
/dissector assert not reached/ ???
Well, it means the dissector got to someplace in the code which it
should not have. Chances are it is a dissector bug.
Usually such a message is accompanied by the name of the dissect
Am 01.10.2011 11:14, schrieb Stig Bjørlykke:
On Sat, Oct 1, 2011 at 10:59 AM, Helge Kruse wrote:
Where do I find good samples or tutorials to get a glimpse of Lua dissectors?
You can have a look at this presentation:
http://sharkfest.wireshark.org/sharkfest.09/DT06_Bjorlykke_Lua%20Scripting%2
Thanks for the detailed answer :-)
FYI this is a plugin dissector. I have handled the fact that packets are
dissected
out of order and multiple times.
It seems to work fine though I'm aware that what I do does not really
respect wireshark dev. spirit partly because this is ad hoc proprietary
prot
On Oct 2, 2011, at 11:09 PM, fa...@freesurf.fr wrote:
> I made a dissector that so far is used with capture file generated from
> traces by a protocol simulator.
> So it is not realtime ethernet sniffering.
> In the dissector I am gathering data from the read capture file to
> generate a new file
