This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: gdb/2171: No backtrace generated on amd64
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 16 Sep 2006 00:18:01 -0000
- Subject: Re: gdb/2171: No backtrace generated on amd64
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR gdb/2171; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: madcoder@gmail.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/2171: No backtrace generated on amd64
Date: Fri, 15 Sep 2006 20:12:43 -0400
On Sat, Sep 16, 2006 at 12:05:32AM -0000, madcoder@gmail.com wrote:
> And the coredump has debugging symbols in it:
Core dumps do not contain real symbol information.
> > # gdb php core
> > GNU gdb 6.5
> > This GDB was configured as "x86_64-pc-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1".
> > Core was generated by `php -e test.php'.
> > Program terminated with signal 11, Segmentation fault.
> > #0 0x00002aaaac8d1e44 in ?? ()
This is a shared library address. Does info shared work? It looks
like your system libraries are undebuggable, not the binary itself.
--
Daniel Jacobowitz
CodeSourcery