Wireshark · Ethereal-dev: Re: [Ethereal-dev] ASN.1 dissector.

[Matthijs Melchior <mmelchior@xxxxxxxxx>]

Guy Harris wrote:

> On Oct 28, 2003, at 2:55 PM, Matthijs Melchior wrote:
>
>  
>
> > Yes, for now it can be #ifdef'ed out, but I think the info presented
> > there if of more value than just debugging the dissector. I will
> > have to find another solution for giving a dissector a private
> > gui interface....
> >    
>
> What is that information?
>  
This is the full definition of the message type the dissector is using,
including the names and types of all the choices and optional fields.
This give you an idea about stuff that *is* not in a packet but *could* be.
I have found this useful in understanding the protocol by looking at
the messages.

> Is it something very specific to an ASN.1 BER dissector, or is it 
> something that might be of use in other dissectors?  If the latter, 
> perhaps there should be a way for a dissector to construct a data 
> structure and have core Ethereal GUI code display it (and perhaps have 
> Tethereal show it in some fashion).  That's what we do now with 
> protocol trees and preferences (and what I'd like us to do at some 
> point for a number of the statistics constructed by taps).
>  
Well, my stuff is a new window with a 'gtk_tree_view' in it to show
the message element tree together with some info for debugging (which
can be removed by now, but I would like to keep the first column).

An interface to define and fill the tree_store would suit me...
And a context menu would also be useful.


Thanks.

--
Regards,
----------------------------------------------------------------  -o)
Matthijs Melchior                                       Maarssen  /\\
mmelchior@xxxxxxxxx                                  Netherlands _\_v
---------------------------------------------------------------- ----