S390: gdbserver: Don't write guarded storage registers
authorAndreas Arnez <arnez@linux.vnet.ibm.com>
Wed, 21 Mar 2018 16:41:45 +0000 (17:41 +0100)
committerAndreas Arnez <arnez@linux.vnet.ibm.com>
Wed, 21 Mar 2018 16:41:45 +0000 (17:41 +0100)
commitc49bd90bdb03f3013a796ea920830547cacc3c48
treec48dd89339be50eaad7c0663d8848e7ea2cc169a
parent7edb9bd32ba23247a509cbe9d44ccb02da97b66e
S390: gdbserver: Don't write guarded storage registers

On S390, the guarded storage register set is only valid if guarded storage
is active.  Reading/writing the register set yields errors if this is not
the case.  Then gdbserver emits warnings like these:

  Warning: ptrace(regsets_store_inferior_registers): No data available

Apart from confusing the user, this can also lead to test case failures
due to unexpected output.  To suppress this, make the guarded storage
regsets read-only for now.

gdb/gdbserver/ChangeLog:

* linux-s390-low.c (s390_fill_gs): Remove function.
(s390_fill_gsbc): Remove function.
(s390_regsets): Set fill functions for the guarded storage regsets
to NULL.
gdb/gdbserver/ChangeLog
gdb/gdbserver/linux-s390-low.c