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: "Joe Hansche" <madcoder at gmail dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 17 Sep 2006 23:08:01 -0000
- Subject: Re: gdb/2171: No backtrace generated on amd64
- Reply-to: "Joe Hansche" <madcoder at gmail dot com>
The following reply was made to PR gdb/2171; it has been noted by GNATS.
From: "Joe Hansche" <madcoder@gmail.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/2171: No backtrace generated on amd64
Date: Sun, 17 Sep 2006 17:04:13 -0600
> Sorry, I wasn't clear enough - neither these nor your later
> off-list message are the right entries. The first column is a physical
> file offset, and is not particularly interesting. The intersting bit
> is the second column: virtual address, e.g. 0x0000000000635070. Is
> that covered by any LOAD?
The first LOAD entry has a VirtAddr value of 0x00002aaaaaaab000, and
the values continue to increase until 0x00007fffff7fa000. So, all of
the values from the coredump are far above the value from the PHP
binary: 0x0000000000635070. I'm sorry I don't quite know what that
means in my case. Would it be more likely that it's a problem with my
PHP, gdb, or kernel? Any suggestions I should try? I can attach my
kernel config if it will be helpful?
Thanks,
Joe
> It'd be a kernel version, but I don't remember which. I think 2.6.15
> is far too new to have the problem, but I don't remember for sure.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>