This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: GDB doesnot catches segmentation fault
- From: Mahmood Naderan <nt_mahmood at yahoo dot com>
- To: "pmuldoon at redhat dot com" <pmuldoon at redhat dot com>
- Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Tue, 5 Jul 2011 00:24:21 -0700 (PDT)
- Subject: Re: GDB doesnot catches segmentation fault
- References: <1309847935.50900.YahooMailNeo@web111702.mail.gq1.yahoo.com> <m3oc19urna.fsf@redhat.com>
- Reply-to: Mahmood Naderan <nt_mahmood at yahoo dot com>
>Then:
>gdb gdb --core=yourcore.pid
>Where "youcore.pid" is the core-file that GDB generated on crash
Where does it save that file? I can not find it
// Naderan *Mahmood;
----- Original Message -----
From: Phil Muldoon <pmuldoon@redhat.com>
To: Mahmood Naderan <nt_mahmood@yahoo.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Sent: Tuesday, July 5, 2011 11:43 AM
Subject: Re: GDB doesnot catches segmentation fault
Mahmood Naderan <nt_mahmood@yahoo.com> writes:
> 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.
> 0x0000000000447bfb in Event::initialized (this=0x41ec648) at build/ALPHA_FS/sim/eventq.hh:84
> 84????????? initialized() const
> (gdb) c
> Continuing.
> Segmentation fault
> mahmood@mpc:~$
This looks like GDB crashed with a segmentation fault.
There is not enough information to work with here.? There are two things
you could try: A newer GDB, the problem might already have been
fixed. Or, submit a backtrace for GDB.
If you have debug information installed for GDB you can do this.? I am
not sure of the method for installing debug information for installed
packages with Ubuntu.? But assuming you do have them:
Type:
ulimit -c unlimited
in the terminal where you will launch GDB? (This will allow core-files
to be generated).
Attach GDB to the program (as you did above) and replicate the scenario
to crash GDB.
Then:
gdb gdb --core=yourcore.pid
Where "youcore.pid" is the core-file that GDB generated on crash.
Then type "bt" into GDB.? This will produce a backtrace of the crashing
GDB process.
Then create a bug at:
http://sourceware.org/bugzilla/
for gdb, and paste the "bt" output.? Also include any supplemental
information you think is useful.
Cheers,
Phil