Re: Testsuite failures in gdb.base/callfuncs.exp

[Andreas Schwab <schwab@suse.de>]

Daniel Jacobowitz <drow@false.org> writes:

> On Wed, Jan 31, 2007 at 01:33:26PM +0100, Andreas Schwab wrote:
>> This fixes these testsuite failures on ia64:
>> 
>> FAIL: gdb.base/callfuncs.exp: gdb function calls preserve register contents
>> FAIL: gdb.base/callfuncs.exp: continue after stop in call dummy preserves register contents
>> FAIL: gdb.base/callfuncs.exp: return after stop in call dummy preserves register contents
>> 
>> The problem is that the bspstore register is specially tied with the bsp
>> register, and this can't be controlled by gdb.
>
> How does this work - i.e. how do we guarantee that the restored state
> is equivalent?  Does it indicate extra registers written to the
> register stack?

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.

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."