Ethereal-dev: Re: [Ethereal-dev] seg fault while reading trace file.
There's probably a bug in a dissector which happens to be triggered by
packets that
are common on your network. Ideally, a backtrace from a debugger would be
the most helpful
(see the end of the README file), but that might be hard for you to do if
you're using the Win32
version of Ethereal and you don't have a debug version of Ethereal and you
don't have any
compiler tools on your system.
If you can't produce a backtrace, then send one of your smaller files to
ethereal-dev, or if you
have information in the trace that shouldn't be public, you cand send the
trace to one of the
developers (me). Otherwise, we'll have to see about having you produce a
backtrace, which
will tell us on which line in which file Ethereal/tethereal blew up.
--gilbert
Gerry <skerbg1@xxxxxxxxxxxxxxxxxxxxxxxx> on 11/06/2000 11:47:38 AM
Please respond to gerald.skerbitz@xxxxxxxxxxxxxxxxxxxxxxxx
To: ethereal-dev@xxxxxxxx
cc: (bcc: Gilbert Ramirez/Tivoli Systems)
Subject: [Ethereal-dev] seg fault while reading trace file.
Ethereal Developers,
I have a bunch of sniff files from BlackICE which, when I try to analyzze
them with tethereal (or ethereal) causes it to seg fault.
It does it with all of these files, but it takes a while for it to happen.
It also doesn't happen consistently.
Would you be interested in the details of this problem?
What information can I send you if you are interested?
Thanks,
Gerry
--
Gerald Skerbitz,
MN Department of Health, Environmental Health
Information Resources Management (MDH/EH/IRM)
gerald.skerbitz@xxxxxxxxxxxxxxxxxx, 215-0740
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
