Possible bug in tcptrace 6.6.7

From: Tim Everitt (tim.everitt@yr20.com)
Date: 09/13/05


From: "Tim Everitt" <tim.everitt@yr20.com>
Subject: Possible bug in tcptrace 6.6.7
Date: Tue, 13 Sep 2005 13:46:34 +0100
Message-Id: <20050913124633.1FA4F450474@relay1.r1.iad.emailsrvr.com>

I have been analyzing some libpcap traces collected using T&M hardware that
collects all Ethernet frames including runts etc.

I have encountered predictable segmentation faults in tcptrace 6.6.7 built
from source and running on RedHat Fedora Core 4.

I *believe* that the errors are associated with runt frames in the libpcap
file.

The file opens correctly using other libpcap compatible tools such as
ethereal but shows the runts.

If anyone is interested then I can send in a small (50 frames, 8Kbytes)
libpcap trace that reliably exhibits this behaviour.

Many thanks for tcptrace which is a remarkable tool. I use it in supporting
RealTime control systems in the offshore oil & gas industry.

Regards, Tim Everitt.
www.yr20.com
tim.everitt@yr20.com

----------------------------------------------------------------------------
To unsubscribe, send a message with body containing "unsubscribe tcptrace" to
majordomo@tcptrace.org.



This archive was generated by hypermail 2.1.7 : 09/13/05 EDT