Hi,
Backtrace file is attached.
Thanks,
On 8/5/2011 2:32 AM, Guy Harris wrote:
On Aug 4, 2011, at 12:25 PM, Roland Knall wrote:
An exception in packet.c can be nearly anything. The backtrace is what
I am looking for,
Yes, as I said. My point is that sending us the core dump won't necessarily make it possible for us to get a backtrace; getting the backtrace on the machine where the crash was occurring, and just sending us the backtrace, would work far better (and result in a much smaller mail message - the backtrace is a lot fewer bytes than the core dump).
___________________________________________________________________________
Sent via: Wireshark-dev mailing list<wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
GNU gdb (GDB) Fedora (7.1-34.fc13)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
[New Thread 21020]
Core was generated by `/home/thang/software/wireshark-1.6.1/.libs/lt-wireshark'.
Program terminated with signal 6, Aborted.
#0 0x00b42416 in __kernel_vsyscall ()
[?1034h(gdb) backtrace
#0 0x00b42416 in __kernel_vsyscall ()
#1 0x005a7bd1 in ?? ()
#2 0x00703ff4 in ?? ()
#3 0x005a94aa in ?? ()
#4 0x00000006 in ?? ()
#5 0xbfa17150 in ?? ()
#6 0x002b9264 in ?? ()
#7 0x09fee4a8 in ?? ()
#8 0x002b980e in ?? ()
#9 0x00000000 in ?? ()
(gdb) quit