diff options
author | Andreas Arnez <arnez@linux.vnet.ibm.com> | 2015-05-08 12:50:47 +0200 |
---|---|---|
committer | Andreas Krebbel <krebbel@linux.vnet.ibm.com> | 2015-05-08 12:50:47 +0200 |
commit | 2492f0d005f0390eabb3deb58aa7db7fcd716763 (patch) | |
tree | d89f1ac63655d58b5b5df9bd8396ce26995dfb76 /gdb/gdbserver/target.h | |
parent | 63fc80ce17311913e41ccb671641310e4ce29eaf (diff) | |
download | gdb-2492f0d005f0390eabb3deb58aa7db7fcd716763.zip gdb-2492f0d005f0390eabb3deb58aa7db7fcd716763.tar.gz gdb-2492f0d005f0390eabb3deb58aa7db7fcd716763.tar.bz2 |
S390: Fix for inadvertently setting 24-bit mode in fill_gregset
On 64-bit S390 platforms, for programs compiled with -m31, it could
happen that GDB inadvertently cleared the inferior's 31-bit addressing
mode bit and left the inferior running in 24-bit addressing mode. In
particular this occurred with checkpoint.exp, when the "restore"
command needed to create a new regcache copy: At the time when the
PSWM register was copied over, the addressing mode bit was taken from
the PSWA register, which was still zero since it had not been copied
yet. And when the PSWA register was copied, the addressing mode was
not updated again.
The fix affects fill_gregset, where the bits "belonging" to each of
the PSWA and PSWM registers are now carefully separated. The
addressing mode bit is no longer touched when writing PSWM, and --
more importantly -- it *is* written when writing PSWA.
gdb/ChangeLog:
* s390-linux-nat.c (fill_gregset): Avoid relying on the PSWA
register in the regcache when treating the PSWM register, and vice
versa.
Diffstat (limited to 'gdb/gdbserver/target.h')
0 files changed, 0 insertions, 0 deletions