gdb/2171: No backtrace generated on amd64

Joe Hansche madcoder@gmail.com
Mon Sep 18 12:28:00 GMT 2006


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: Mon, 18 Sep 2006 06:21:40 -0600

 I've upgraded to kernel version 2.6.17, with the same results (after
 recompiling both gdb and php).  I tried looking through the kernel
 .config to see what might cause something like this.  The only thing I
 ended up changing, aside from the defaults in the new kernel, was
 changing the memory model from Discontiguous to Sparse.
 
 Any more ideas?  Or since you are saying it looks like a kernel
 problem, where should I look for more information on this?
 
 Thanks again,
 Joe
 
 On 9/17/06, Daniel Jacobowitz <drow@false.org> wrote:
 > On Sun, Sep 17, 2006 at 05:04:13PM -0600, Joe Hansche wrote:
 > > 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?
 >
 > It wouldn't be helpful.  I can only guess that the kernel is at fault.
 >
 > --
 > Daniel Jacobowitz
 > CodeSourcery
 >



More information about the Gdb-prs mailing list