aboutsummaryrefslogtreecommitdiff
path: root/gdb/hppa-hpux-tdep.c
diff options
context:
space:
mode:
authorAndreas Arnez <arnez@linux.vnet.ibm.com>2015-01-14 17:53:23 +0000
committerUlrich Weigand <ulrich.weigand@de.ibm.com>2015-02-04 14:14:31 +0100
commitdde9acd693251ccbe28d2d9c6c8b3cdc8ca884ed (patch)
tree6679b94d2f7bb2fbc9a2c74526e9ed01082aa30d /gdb/hppa-hpux-tdep.c
parent1528345d6c4a407e0b36b3474eb458cbd04146f7 (diff)
downloadgdb-dde9acd693251ccbe28d2d9c6c8b3cdc8ca884ed.zip
gdb-dde9acd693251ccbe28d2d9c6c8b3cdc8ca884ed.tar.gz
gdb-dde9acd693251ccbe28d2d9c6c8b3cdc8ca884ed.tar.bz2
x86: Use correct .reg-xstate section size
When reading the XSAVE extended state from an i386 or AMD64 core file, the respective regset iterator requests a minimum section size of zero. Since the respective regset supply function does not check the size either, this may lead to accessing data out of range if the section is too short. In write mode, the iterator always uses the maximum supported size for the XSAVE extended state. This is now changed such that the iterator always requests the expected size of this section based on xcr0, both for reading and writing. gdb/ChangeLog: * amd64-linux-tdep.c (amd64_linux_iterate_over_regset_sections): For ".reg-xstate", explicitly specify the requested section size via X86_XSTATE_SIZE instead of just 0 on input and X86_XSTATE_MAX_SIZE on output. * i386-linux-tdep.c (i386_linux_iterate_over_regset_sections): Likewise.
Diffstat (limited to 'gdb/hppa-hpux-tdep.c')
0 files changed, 0 insertions, 0 deletions