This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
GDB doesnot catches segmentation fault
- From: Mahmood Naderan <nt_mahmood at yahoo dot com>
- To: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Mon, 4 Jul 2011 23:38:55 -0700 (PDT)
- Subject: GDB doesnot catches segmentation fault
- Reply-to: Mahmood Naderan <nt_mahmood at yahoo dot com>
Hi
I have attached a PID to gdb. Although the code crashed with segmentation fault, but gdb ignores that and I am not able to view backtrace.
The output of my program is
...
loading script...
Begin simulation
Segmentation fault
Done :D
....
and the gdb output on another terminal contains
mahmood@mpc:~$ gdb - 23425
GNU gdb (GDB) 7.1-ubuntu
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 "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
-: No such file or directory.
Attaching to process 23425
Reading symbols from /home/mahmood/gem5/build/ALPHA_FS/m5.debug...done.
Reading symbols from /lib/libpthread.so.0...(no debugging symbols found)...done.
[Thread debugging using libthread_db enabled]
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/libutil.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libutil.so.1
Reading symbols from /usr/lib/libpython2.6.so.1.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libpython2.6.so.1.0
Reading symbols from /lib/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libz.so.1
Reading symbols from /lib/librt.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/librt.so.1
Reading symbols from /usr/lib/libstdc++.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libstdc++.so.6
Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /lib/libgcc_s.so.1...Reading symbols from /usr/lib/debug/lib/libgcc_s.so.1...done.
done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /lib/libssl.so.0.9.8...(no debugging symbols found)...done.
Loaded symbols for /lib/libssl.so.0.9.8
Reading symbols from /lib/libcrypto.so.0.9.8...(no debugging symbols found)...done.
Loaded symbols for /lib/libcrypto.so.0.9.8
Reading symbols from /usr/lib/python2.6/lib-dynload/datetime.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/python2.6/lib-dynload/datetime.so
0x0000000000447bfb in Event::initialized (this=0x41ec648) at build/ALPHA_FS/sim/eventq.hh:84
84????????? initialized() const
(gdb) c
Continuing.
Segmentation fault
mahmood@mpc:~$
Any idea bout that?
?
// Naderan *Mahmood;