This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: gdb/1286: stack trace screwed on ia64
- From: Steve Ellcey <sje at cup dot hp dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 13 Jan 2004 18:38:00 -0000
- Subject: Re: gdb/1286: stack trace screwed on ia64
- Reply-to: Steve Ellcey <sje at cup dot hp dot com>
The following reply was made to PR gdb/1286; it has been noted by GNATS.
From: Steve Ellcey <sje@cup.hp.com>
To: gdb-gnats@sources.redhat.com, nobody@sources.redhat.com,
david@streamline-computing.com, gdb-prs@sources.redhat.com
Cc:
Subject: Re: gdb/1286: stack trace screwed on ia64
Date: Tue, 13 Jan 2004 10:35:28 -0800
David,
I just tried to reproduce your GDB defect 1286 with GDB 6.0 and it looks
like the problem is fixed in the new version of GDB. I was wondering if
you think this defect can now be closed.
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=1286
Using your test program on IA64 Redhat Linux 2.4.21-4.EL and a GDB 6.0
that I built:
(gdb) break main
Breakpoint 1 at 0x4000000000000672: file Buggy.c, line 10.
(gdb) run
Starting program: /tmp/sje/x
Breakpoint 1, main (argc=1, argv=0x60000fffffffbb08) at Buggy.c:10
10 t2 = malloc(4);
(gdb) next
12 for(p=0;p<100;p++)
(gdb) bt
#0 main (argc=1, argv=0x60000fffffffbb08) at Buggy.c:12
This output looks OK to me.
Steve Ellcey
sje@cup.hp.com