This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
backtrace/1750: gdb6.2 reports corrupt stack, but gdb4.17 doesn't
- From: ntoze at ufji dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 16 Aug 2004 16:31:33 -0000
- Subject: backtrace/1750: gdb6.2 reports corrupt stack, but gdb4.17 doesn't
- Reply-to: ntoze at ufji dot com
>Number: 1750
>Category: backtrace
>Synopsis: gdb6.2 reports corrupt stack, but gdb4.17 doesn't
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Aug 16 16:38:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: ntoze
>Release: GNU gdb 6.2
>Organization:
>Environment:
$ uname -a
SunOS canopus 5.8 Generic_108528-14 sun4u sparc SUNW,Ultra-4
I compiled gdb with gcc 2.95.2
>Description:
gdb6.2 reports corrupt stack, but gdb4.17 can trace back to main().
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: