Ethereal-dev: Re: [Ethereal-dev] patch for packet-ncp2222.inc to fix GLIB-CRITICAL error.

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

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Guy Harris <guy@xxxxxxxxxx>
Date: Tue, 25 Feb 2003 12:47:34 -0800
On Tue, Feb 25, 2003 at 01:35:47PM -0700, Greg Morris wrote:
> I hate to appear dumb but is the reason for this because after the
> trace has been opened and dissected then if you filter the trace then
> the lookup will not be processed on these packets because they already
> have the flag set?

That's one reason.

Another reason is that if you subsequently click on a packet the lookup
will not be processed on that packet because it already has the flag
set, and if you ask Ethereal to print the packets the lookup will not be
processed on that packet because it already has the flag set, etc..

> If so would it be better to leave the hash until the trace is closed?

If only one value is associated with a given EID (i.e., if the
association of values with EIDs doesn't change over time), yes, that'd
be the right answer.