Wireshark · Ethereal-dev: SV: [Ethereal-dev] What's changed with operational dissection?

["Anders Broman" <a.broman@xxxxxxxxx>]

Hi,
The problem is probably because of TRY_TO_FAKE_THIS_ITEM used to speed up
the dissection.

To get the console open edit preferences and set "Open a consol window" as
desired. 

Brg
Anders

-----Ursprungligt meddelande-----
Från: ethereal-dev-bounces@xxxxxxxxxxxx
[mailto:ethereal-dev-bounces@xxxxxxxxxxxx] För Jaap Keuter
Skickat: den 27 oktober 2005 18:48
Till: Ethereal Developer Mailinglist
Ämne: [Ethereal-dev] What's changed with operational dissection?

Hi list,

I've been asked to port some dissectors from 0.10.11 to 0.10.13.
In doing that I've bumped into this thing.
When a certain packet is dissected it creates a conversation, adds a 32
bit value to it and is done. A packet further down the line can look for
this conversation, get the value and adjust its display accordingly.

Now what I see differently from 0.10.11 is that I have to have a detailed
dissection done on the packet creating the conversation in order for the
packet further sown the line to find it. There seems to be no conversation
without the detailed dissection (no the conversation creation code is not
in an 'if (tree)' block.).

Also what is the current state of the art to get debug output onto the
console window (Win32)?

Thanx,
Jaap


_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev