Ethereal-dev: Re: [Ethereal-dev] Segmentation fault, core dumped ethereal

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

From: Guy Harris <guy@xxxxxxxxxx>
Date: Mon, 22 Jan 2001 16:45:50 -0800 (PST)
Note that the fact that I reply to a mail message reporting a problem
doesn't mean I'm taking ownership of the problem; therefore, replies
shouldn't be sent only to me.

> Yes, I meant to say the files I load or read into the command line with
> "ethereal -r" are stored in /tmp.

Then we'll need, somehow, to get a non-bogus stack trace; a stack trace
reporting that a procedure call came from an array of structures is
definitely bogus.

Try running Ethereal from within GDB and, when it stops with a signal
when reading in the capture, try doing the stack trace then to see if it
gives a better stack trace.

Also, you may have to recompile GLib and/or GTK+; somebody else
discovered, apparently, that there are some annoying problems with the
latest shiniest GCC and/or the latest shiniest glibc (glibc, not GLib) -
unfortunately, the details I have, from that person's mail, are at home,
so I can't give any more details now (unless that person sees this mail
and responds).