Ethereal-users: Re: [Ethereal-users] bug report: tethereal assertion failed, file proto.c, line

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: Fri, 29 Jun 2001 19:53:53 -0700 (PDT)
> I believe I found a bug that causes ethereal or tethereal to crash on
> a certain packet.

Yes, it tends to blow up on frames from some ONC RPC-based protocols. 
The current CVS version has those bugs fixed.

> With ethereal, the packet loads okay unless you're using a filter, or
> click on that particular packet.

It happens when the frame is fully dissected, generating a protocol
tree.  (If it's not generating a protocol tree, it doesn't call the
routine that blows up.) If you click on the packet, it has to generate
the protocol tree, so that it can display it; it also has to do so in
order to evaluate a display filter.

> With tethereal, the packet gets
> displayed okay unless you're using a filter or '-V' mode.

Same issue - "-V" prints the full dissection, and the filter requires
the protocol tree to be generated.