This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: backtrace/1437: gdb fails to print backtrace: Cannot access memory at address 0xbf800000 in Linux/gcc/C
- From: Mark Kettenis <kettenis at chello dot nl>
- To: kettenis at gnu dot org
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 31 Oct 2003 17:08:00 -0000
- Subject: Re: backtrace/1437: gdb fails to print backtrace: Cannot access memory at address 0xbf800000 in Linux/gcc/C
- Reply-to: Mark Kettenis <kettenis at chello dot nl>
The following reply was made to PR backtrace/1437; it has been noted by GNATS.
From: Mark Kettenis <kettenis@chello.nl>
To: gdb-gnats@sources.redhat.com, bjacob@ca.metsci.com, kettenis@gnu.org,
gdb-prs@sources.redhat.com
Cc:
Subject: Re: backtrace/1437: gdb fails to print backtrace: Cannot access memory at address 0xbf800000 in Linux/gcc/C
Date: Fri, 31 Oct 2003 18:05:26 +0100 (CET)
I don't think this is a GDB bug. By recursively calling your function
f() you probably ran out of stack space, which means that the stack
pointer points to somwhere below the allocated stack space. The Linux
kernel only dumped the part of the stack that was properly allocated,
so the bit of memory where the stack pointer points at isn't there
anymore. The result is that it is impossible to produce a backtrace.
Mark