Wireshark mailing list archives
Re: Inconsistent availability of proto_tree values during the first of two passes
From: Paul Offord <Paul.Offord () advance7 com>
Date: Sun, 9 Apr 2017 20:07:27 +0000
So if I add code to TRANSUM so that it only registers itself when running with Wireshark, would that be acceptable as a fix pending the redesign and recoding as you have described below? -----Original Message----- From: wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of Guy Harris Sent: 09 April 2017 21:01 To: Developer support list for Wireshark <wireshark-dev () wireshark org> Subject: Re: [Wireshark-dev] Inconsistent availability of proto_tree values during the first of two passes On Apr 9, 2017, at 12:48 PM, Paul Offord <Paul.Offord () advance7 com> wrote:
As making the code consistent has been rejected and the tap idea won’t work, where do we go from here?
As somebody said:
We might also want a way to have taps/"post-"dissectors that act as extensions to particular protocol dissectors - that might be what TRANSUM, and possibly MATE, *really* want to be.)
and as somebody said in https://www.wireshark.org/lists/wireshark-dev/201702/msg00082.html
Alternatively, we could have a set of flags used when post-dissectors are registered, including "this post-dissector needs a protocol tree", and, if there are any active post-dissectors that require a protocol tree, one will be generated.
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe ______________________________________________________________________ This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour House, Coopers End Lane, Stansted, Essex CM24 1SJ ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Inconsistent availability of proto_tree values during the first of two passes Paul Offord (Apr 09)
- Re: Inconsistent availability of proto_tree values during the first of two passes Guy Harris (Apr 09)
- Re: Inconsistent availability of proto_tree values during the first of two passes Paul Offord (Apr 09)
- Re: Inconsistent availability of proto_tree values during the first of two passes Guy Harris (Apr 09)
- Re: Inconsistent availability of proto_tree values during the first of two passes Paul Offord (Apr 09)
- Re: Inconsistent availability of proto_tree values during the first of two passes Guy Harris (Apr 09)
- Re: Inconsistent availability of proto_tree values during the first of two passes Paul Offord (Apr 09)
- Re: Inconsistent availability of proto_tree values during the first of two passes Guy Harris (Apr 09)
- Re: Inconsistent availability of proto_tree values during the first of two passes Paul Offord (Apr 10)
- Re: Inconsistent availability of proto_tree values during the first of two passes Guy Harris (Apr 10)
- Re: Inconsistent availability of proto_tree values during the first of two passes Paul Offord (Apr 10)
- Re: Inconsistent availability of proto_tree values during the first of two passes Guy Harris (Apr 10)
- Re: Inconsistent availability of proto_tree values during the first of two passes Paul Offord (Apr 10)
- Re: Inconsistent availability of proto_tree values during the first of two passes Paul Offord (Apr 09)
- Re: Inconsistent availability of proto_tree values during the first of two passes Guy Harris (Apr 09)