* Re: GDB 6.0 backtrace only prints 4 stack frames
@ 2003-10-08 17:27 Dana, Eric
2003-10-08 17:59 ` Andrew Cagney
0 siblings, 1 reply; 3+ messages in thread
From: Dana, Eric @ 2003-10-08 17:27 UTC (permalink / raw)
To: 'gdb@sources.redhat.com'
>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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: GDB 6.0 backtrace only prints 4 stack frames
2003-10-08 17:27 GDB 6.0 backtrace only prints 4 stack frames Dana, Eric
@ 2003-10-08 17:59 ` Andrew Cagney
0 siblings, 0 replies; 3+ messages in thread
From: Andrew Cagney @ 2003-10-08 17:59 UTC (permalink / raw)
To: Dana, Eric; +Cc: 'gdb@sources.redhat.com'
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* GDB 6.0 backtrace only prints 4 stack frames
@ 2003-10-07 16:23 Paul Dubuc
0 siblings, 0 replies; 3+ messages in thread
From: Paul Dubuc @ 2003-10-07 16:23 UTC (permalink / raw)
To: GDB Mailing List
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?
--
Paul M. Dubuc mailto:pdubuc@cas.org
Room 4349B (614) 447-3600 x2692
http://www.purl.org/dubuc/cas/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-10-08 17:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-10-08 17:27 GDB 6.0 backtrace only prints 4 stack frames Dana, Eric
2003-10-08 17:59 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-10-07 16:23 Paul Dubuc
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox