RE: [PATCH 2/2 ] PowerPC: fix for gdb.reverse/finish-precsave.exp and gdb.reverse/finish-reverse.exp

[Carl Love <cel@us.ibm.com>]

Simon:

On Mon, 2023-03-27 at 21:19 -0400, Simon Marchi wrote:
> To confirm the theory, I added a:
> 
>    gdb_test "set range-stepping off"
> 
> somewhere near the beginning of your test, and it makes the test pass
> with native-gdbserver.
> 
> If we want recording to work the same with process targets using
> range-stepping and those that don't, maybe GDB should avoid using
> range-stepping when the record-full target is in effect?

We could just update the test to include gdb_test "set range-stepping
off" with a brief explanation of the issue. This would have a minimal
impact on performance of this test and no performance degradation for
any other tests.  It sounds like this would fix the issue for just this
test. 

It sounds like disabling range-stepping when record-full is enabled
would be the more general fix for the issue.  Not sure if there are
other tests where this issue occurs.  Doing the more general fix would
probably have some performance impact on the other tests that need to
use record-full. I can't really say how much of an impact it would be.

Thanks for the insight on how gdbserver works.  At this point, I have
not looked into that part of gdb.  

                            Carl