Wireshark mailing list archives
Re: Bug in Wireshark Display filter engine caused by optimization of proto tree during dissect
From: mmann78 () netscape net
Date: Fri, 21 Aug 2015 10:47:25 -0400
Anders kind of beat me too it, but there are ways other than storing it in packet_info to exchange the data. I don't know enough about the dissectors themselves to suggest the "best" way, but please don't consider packet_info as an option. -----Original Message----- From: Richard Sharpe <realrichardsharpe () gmail com> To: Developer support list for Wireshark <wireshark-dev () wireshark org> Sent: Fri, Aug 21, 2015 10:38 am Subject: Re: [Wireshark-dev] Bug in Wireshark Display filter engine caused by optimization of proto tree during dissect Right, this would be a better approach if people are not too uncomfortable in storing this piece of info. Thus, the radiotap (and perhaps one other in the tree that seems to know the channel frequency) could store it as a value in the pinfo. These changes would be much less intrusive in the rest of the infrastructure and confined to the ieee80211 series of dissectors. -- Regards, Richard Sharpe (何以解憂?唯有杜康。--曹操) ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Bug in Wireshark Display filter engine caused by optimization of proto tree during dissect Richard Sharpe (Aug 21)
- Re: Bug in Wireshark Display filter engine caused by optimization of proto tree during dissect Jeff Morriss (Aug 21)
- Re: Bug in Wireshark Display filter engine caused by optimization of proto tree during dissect Richard Sharpe (Aug 21)
- Re: Bug in Wireshark Display filter engine caused by optimization of proto tree during dissect Anders Broman (Aug 21)
- Re: Bug in Wireshark Display filter engine caused by optimization of proto tree during dissect Hadriel Kaplan (Aug 21)
- Re: Bug in Wireshark Display filter engine caused by optimization of proto tree during dissect Anders Broman (Aug 21)
- Re: Bug in Wireshark Display filter engine caused by optimization of proto tree during dissect Richard Sharpe (Aug 21)
- Re: Bug in Wireshark Display filter engine caused by optimization of proto tree during dissect Richard Sharpe (Aug 21)
- Re: Bug in Wireshark Display filter engine caused by optimization of proto tree during dissect mmann78 (Aug 21)
- Re: Bug in Wireshark Display filter engine caused by optimization of proto tree during dissect Jeff Morriss (Aug 21)
- Re: Bug in Wireshark Display filter engine caused by optimization of proto tree during dissect Guy Harris (Aug 21)
- Re: Bug in Wireshark Display filter engine caused by optimization of proto tree during dissect Richard Sharpe (Aug 21)