Re: stable release 1.6.1 is core dumped on Fedora 13, 15

[Roland Knall <rknall () gmail com>]

An exception in packet.c can be nearly anything. The backtrace is what
I am looking for, as it would tell which dissector caused the
underlying issue.

Roland



Am 04.08.2011 um 21:23 schrieb Guy Harris <guy () alum mit edu>:

> On Aug 4, 2011, at 10:47 AM, Roland Knall wrote:
>
> > There should be a file called core in the directory you called Wireshark from. Please send this file.
>
> More precisely, "please send this file, and the entire build directory for Wireshark, to somebody also running the 
> same version of Fedora".  Core dumps can't really be interpreted without the executable image that produced them and 
> all the dynamically-loaded libraries (and, if the crash occurred in a run-time-loaded plugin, the plugin in 
> question), including system libraries, it was using at the time - and at least some symbols are needed as well.
>
> An alternative would be to run the debugger (gdb, probably) on the core dump and run the command to print a stack 
> trace ("backtrace" or "bt", for gdb) and send us the stack trace.
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe