diff options
author | Andrew Burgess <aburgess@redhat.com> | 2024-03-27 14:30:48 +0000 |
---|---|---|
committer | Andrew Burgess <aburgess@redhat.com> | 2024-06-14 09:08:45 +0100 |
commit | 1845af06191e7a457010b943d06628af731b4549 (patch) | |
tree | 843069e1da61fd72250fadd112be1cf55f91c6ee /COPYING | |
parent | fab07978eca3bfcfa8ba43bce0e38f5340bffd8e (diff) | |
download | gdb-1845af06191e7a457010b943d06628af731b4549.zip gdb-1845af06191e7a457010b943d06628af731b4549.tar.gz gdb-1845af06191e7a457010b943d06628af731b4549.tar.bz2 |
gdb: move xcr0 == 0 check into i386_linux_core_read_description
Currently, in i386_linux_core_read_description, if GDB fails to
extract an xcr0 value from the core file, then we will have a default
zero value for the xcr0 variable, we still call the
i386_linux_read_description function, which checks for this zero value
and returns nullptr.
Back in i386_linux_core_read_description we spot the nullptr return
value from i386_linux_read_description and call
i386_linux_read_description again, but this time passing a default
value for xcr0.
In the next commit I plan to rework i386_linux_read_description, and
in so doing I will remove the check for xcr0 == 0, this is inline with
how the amd64 code is written.
However, this means that the 'xcr0 == 0' check needs to move up the
stack to i386_linux_core_read_description, again, this brings the i386
code into line with the amd64 code.
This is just a refactor in preparation for the next commit, there
should be no user visible changes after this commit.
Approved-By: Felix Willgerodt <felix.willgerodt@intel.com>
Approved-By: John Baldwin <jhb@FreeBSD.org>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions