On Thursday, July 17, 2003, at 2:50 PM, Robert Denton wrote:
Does anyone know if ethereal is supposed to be stable on RedHat 9? I
have
just installed and updated it and it seems to crash after just a few
seconds
of capture pretty consistently.
This doesn't necessarily have anything to do with Red Hat 9, or Red
Hat, or Linux in general. If either
1) you weren't doing an "Update list of packets in real time" capture
and it didn't crash until after you stopped the capture
or
2) you were doing an "Update list of packets in real time" capture
then it's probably a bug in a dissector - i.e., it's an issue of the
traffic that happens to be on your network.
The README file says:
How to Report a Bug
-------------------
Ethereal is still under constant development, so it is possible that
you will
encounter a bug while using it. Please report bugs to
ethereal-dev@xxxxxxxxxxxx.
Be sure you tell us:
1) Operating System and version (the command 'uname -sr' may
tell you this, although on Linux systems it will probably
tell you only the version number of the Linux kernel, not of
the distribution as a whole; on Linux systems, please tell us
both the version number of the kernel, and which version of
which distribution you're running)
2) Version of GTK+ (the command 'gtk-config --version' will tell you)
3) Version of Ethereal (the command 'ethereal -v' will tell you,
unless the bug is so severe as to prevent that from working,
and should also tell you the versions of libraries with which
it was built)
4) The command you used to invoke Ethereal, and the sequence of
operations you performed that caused the bug to appear
If the bug is produced by a particular trace file, please be sure to
send
a trace file along with your bug description. Please don't send a trace
file
greater than 1 MB when compressed. If the trace file contains sensitive
information (e.g., passwords), then please do not send it.
If Ethereal died on you with a 'segmentation violation', 'bus error',
'abort', or other error that produces a UNIX core dump file, you can
help the developers a lot if you have a debugger installed. A stack
trace can be obtained by using your debugger ('gdb' in this example),
the ethereal binary, and the resulting core file. Here's an example of
how to use the gdb command 'backtrace' to do so.
$ gdb ethereal core
(gdb) backtrace
..... prints the stack trace
(gdb) quit
$
The core dump file may be named "ethereal.core" rather than "core" on
some platforms (e.g., BSD systems). If you got a core dump with
Tethereal rather than Ethereal, use "tethereal" as the first argument to
the debugger; the core dump may be named "tethereal.core".
