Wireshark mailing list archives
Re: Make "giop plugins" built in dissectors?
From: Jeff Morriss <jeff.morriss.ws () gmail com>
Date: Tue, 05 Jun 2012 14:26:29 -0400
Tyson Key wrote:
Hi Jeff,I've also noticed that with a modern x86-64-based machine (with 3GB of RAM, and a triple-core AMD Phenom II CPU), and a recent-ish version of GCC running under *buntu. It certainly seems like a good stress test for any compiler/OS/machine combination.With that in mind, just what is packet-parlay.c being used for, anyway? (And why is it so large?)Apologies in advance for the stupid questions,
Well, I think that the problem is mostly that it's a generated dissector. For a big protocol.
But I admit I haven't looked in depth. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Re: Make "giop plugins" built in dissectors? Alexis La Goutte (Jun 01)
- <Possible follow-ups>
- Re: Make "giop plugins" built in dissectors? Jeff Morriss (Jun 05)
- Re: Make "giop plugins" built in dissectors? Gerald Combs (Jun 05)
- Re: Make "giop plugins" built in dissectors? Tyson Key (Jun 05)
- Re: Make "giop plugins" built in dissectors? Jeff Morriss (Jun 05)
- Re: Make "giop plugins" built in dissectors? Jeff Morriss (Jun 05)