GDB 6.0 backtrace only prints 4 stack frames

Andrew Cagney ac131313@redhat.com
Wed Oct 8 17:59:00 GMT 2003


> I've just downloaded GDB 6.0 and built it for Solaris 2.8.  When examining
>>a core from a program (compiled with GNU g++ 2.95.3), the "backtrace" (or
>>"where") command only prints stack frames 0-3 for each thread. Passing a
>>number larger than 4 to the command makes no difference.  This isn't a
>>problem with gdb 5.3. Is this a known bug?
> 
> 
> We have been experiencing the same problem on Solaris 2.8 32-bit while
> debugging
> a shared library.
> 
> Eric Dana
> BMC Software Inc.

Likely this:

> mips*-*-*
> powerpc*-*-*
> sparc*-*-*
> 
> GDB's SPARC, MIPS and PowerPC targets, in 6.0, have not been updated
> to use the new frame mechanism.
> 
> People encountering problems with these targets should consult GDB's
> web pages and mailing lists (http://www.gnu.org/software/gdb/) to see
> if there is an update.

from the PROBLEMS file.  There's a new sparc branch to help people work 
on it in the mainline.

Andrew




More information about the Gdb mailing list