Ethereal-dev: Re: [Ethereal-dev] The Thing - check in the files ?

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date: Thu, 18 Nov 2004 03:12:35 +0100
> Hm    so you also want to insert stuff in the dissect pane tree?

Yes, that's the thing's purpose, to have a tree that contains
information from other frames so It can be used, for example, to
filter all packets of a call knowing just the calling number.

If I call proto_item_add_xxx from the tap listener it just crashes.

I have to call  "thing_tree()" ( the one that calls
proto_item_add_xxx) from somewhere else. AFAIK I would need either a
hook that calls the dissector after every one else (preety much what I
used to do in packet.c )

attached you'll find the least intrusive way I found to do it.
 
I'd like not to touch any files other than mine but I'm not able.

Luis
> 
> Is there no way to go from  an EDT entry into an proto_item *   so you
> can just do a proto_item_add_xxx()     ?
> 
> On Thu, 18 Nov 2004 02:00:57 +0100, LEGO <luis.ontanon@xxxxxxxxx> wrote:
> > I did, at least one part of it...
> >
> > I changed do_thing to be a tap listener, it imports the fields and it
> > does its job.
> > I did delete file.c and packet.c and restored them from svn.
> >
> > part 1 is solved...
> >
> > part 2 is:
> > just calling thing_tree() from the tap against edt->tree did not realy work.
> >
> > Now the issue bocomes: how do I get the thing's tree into the tree?
> >
> > Unfortunatelly I have thought no viable way but to call it from
> > somewhere where it will gets actually called every time the tree has
> > to be displayed. That is either packet.c or packet-frame.c, am I
> > wrong?
> >
> > even in the case I'm not wrong and we need to meke it somehow
> > intrusive, there's a huge progress, now the "intrusion" needed is no
> > more than five lines of code in one of those files.
> >
> > Luis
> >
>

Attachment: packet-frame.c.patch
Description: Binary data