This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Testsuite failures in gdb.base/callfuncs.exp
- From: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- To: drow at false dot org
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 1 Feb 2007 23:53:34 +0100 (CET)
- Subject: Re: Testsuite failures in gdb.base/callfuncs.exp
- References: <jebqkf9y09.fsf@sykes.suse.de> <20070131124926.GA18380@nevyn.them.org> <je3b5r9u67.fsf@sykes.suse.de> <20070131141530.GA22362@nevyn.them.org> <jey7nj8csm.fsf@sykes.suse.de> <20070131151001.GA25714@nevyn.them.org>
> Date: Wed, 31 Jan 2007 10:10:01 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> On Wed, Jan 31, 2007 at 03:56:57PM +0100, Andreas Schwab wrote:
> > Daniel Jacobowitz <drow@false.org> writes:
> >
> > > On Wed, Jan 31, 2007 at 02:56:16PM +0100, Andreas Schwab wrote:
> > >> bsp can only be modified by writing to bspstore, which is what the kernel
> > >> does behind our back. gdb itself never writes to bspstore. Thus the
> > >> value of bspstore does not really matter.
> > >
> > > Could we restore it if we tried?
> >
> > Why would we want to?
>
> I don't know. To leave the inferior's state as untouched as possible
> after an artificial function call.
>
> If you're convinced that's not useful, patch is OK.
No I think there actually is a problem. Either the bspstore matters
or it doesn't. If it doesn't, GDB should just not include it in the
list of registers it displays. If it does matter, the test is showing
a genuine bug.
Mark