Ethereal-dev: Re: [Ethereal-dev] Odd error in Ethereal / iostats

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@xxxxxxxxxxxx>
Date: Mon, 27 Oct 2003 15:04:20 -0800

On Oct 26, 2003, at 7:20 PM, Kevin wrote:
Not sure if this will help, but I have a reproducible error. What other details can I provide?
I couldn't reproduce it with similar filters (I used IP addresses rather than names, but that's probably not the issue). However, the IO stats code has been changed since 0.9.15. 

Try doing

	limit coredumpsize unlimited
and then run Ethereal and try to reproduce the problem. It will (at least on Panther) produce a core dump file in "/cores", which (at least if you've installed the developer tools) you can analyze with "gdb" and get a stack trace. Run 

	gdb {full pathname for ethereal} {full pathname for the core dump file}

and then, within "gdb", run the command "bt".
The Console app might also show you the CrashReporter log for ethereal - at least in Panther, CrashReporter is under ~/Library/Logs, with ethereal.crash.log, if present, under that. That gives you a stack trace, albeit not as good a stack trace as gdb might give.