This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: threads/2395: "info stack" works, but "stack-info-depth" fails
- From: "Øyvind Harboe" <oyvind dot harboe at zylin dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 4 Jan 2008 13:08:01 -0000
- Subject: Re: threads/2395: "info stack" works, but "stack-info-depth" fails
- Reply-to: "Øyvind Harboe" <oyvind dot harboe at zylin dot com>
The following reply was made to PR threads/2395; it has been noted by GNATS.
From: "=?ISO-8859-1?Q?=D8yvind_Harboe?=" <oyvind.harboe@zylin.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: gdb-gnats@sources.redhat.com
Subject: Re: threads/2395: "info stack" works, but "stack-info-depth" fails
Date: Fri, 4 Jan 2008 13:58:37 +0100
n Jan 4, 2008 1:55 PM, Daniel Jacobowitz <drow@false.org> wrote:
> On Fri, Jan 04, 2008 at 10:22:33AM +0100, =D8yvind Harboe wrote:
> > Is it realistic to have this fixed in GDB or should hardware debuggers
> > simply return a garbage value
> > (0xfffff...?) and let the target memory read succeed? Fixing OpenOCD
> > wouldn't be hard.
>
> It's a GDB bug. When someone has time to work on it, we'll fix it in
> GDB. I would call that breaking OpenOCD, not fixing it.
What's the ETA on a fix? I know how to fix OpenOCD, but I wouldn't
know where to start
to fix GDB.
--=20
=D8yvind Harboe
http://www.zylin.com - eCos ARM & FPGA developer kit