Ethereal-dev: Re: [Ethereal-dev] Etheral Crashes by opening a captured file

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

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Mon, 3 Nov 2003 18:51:03 -0800

On Oct 31, 2003, at 4:40 AM, Hirsch, Christian wrote:


If you are in GDB with that stack trace, and on frame 0, what does
"print *handle" report?

look on the bottom of this mail.


Also, could you send us one of those captured files?

Sorry, I would, but I can't. There are many customer data in it.
I can open the full capture file.
But when I insert a filter after I opend it (e.g. gtpv0.imsi == "1234567") ethereal crashed. 

Today I got the same problem on a captured file.
I did the backtrace and "print *handle".

Following my result:

Program received signal SIGSEGV, Segmentation fault.
0x082df21f in call_dissector_work (handle=0x34393333,
That's supposed to be the "handle" for the PPP dissector, but it looks like 4 characters from an ASCII string for a number (if x86, it's probably 3394), not a pointer. 

Something might have overwritten memory due to a bug.

Try Ethereal 0.9.16, to see if it still happens.