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

Andreas Schwab
2007-01-31T15:35:32Z

Daniel Jacobowitz <drow@false.org> writes:

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

We already do that by writing to bsp, which by side effect restores the
state of the RSE as much as possible. The RSE is running in background in
a way that cannot really be controlled by user level anyway.

> If you're convinced that's not useful, patch is OK.

Thanks.

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