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: Andreas Schwab <schwab at suse dot de>
- To: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- Cc: drow at false dot org, gdb-patches at sourceware dot org
- Date: Fri, 02 Feb 2007 00:29:11 +0100
- 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> <200702012253.l11MrYDH006566@brahms.sibelius.xs4all.nl>
Mark Kettenis <mark.kettenis@xs4all.nl> writes:
> 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.
I don't think a register should be left out just because it is read-only.
It is still part of the processor state and can present information that
may be needed for debugging.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."