Ethereal-dev: Re: [Ethereal-dev] file.c strangeness

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

From: "Ronnie Sahlberg" <sahlberg@xxxxxxxxxxxxxxxx>
Date: Mon, 12 Aug 2002 23:57:12 +1000
From: "Khachaturov Vassilii"
Sent: Monday, August 12, 2002 11:32 PM
Subject: RE: [Ethereal-dev] file.c strangeness


> > > Is it really used or should it be removed?
> >
> > I don't know whether any people use read filters either in Ethereal
> > (specified in the "Open Capture File" dialog box or a "-R"
> > command-line
> > option) or in Tethereal (specified with a "-R" command-line option).
>
> I do use it - mostly with tethereal, where it is really needed for me,
> and some times for ethereal - where I could have lived without it.

Ok.  Perhaps if we just keep in mind that if read filters are applied, there
might be "unexpected" results if some of the stateful options are enabled.


Or perhaps the following workaround could work:
During the read-filter run, make pinfo->fd->flags.visited TRUE and then let
it be FALSE
for the displayfilter run.
Most of the options that need pinfo->fd->num to be meaningful are already
encapsulated
inside if(!pinfo->fd->flags.visited){  (for other reasons)
so then perhaps it wouldnt matter much that dissectors are sometimes called
with undefined
settings of pinfo->fd->num.