diff options
author | Andrew Burgess <aburgess@redhat.com> | 2024-01-27 09:15:35 +0000 |
---|---|---|
committer | Andrew Burgess <aburgess@redhat.com> | 2024-06-14 09:08:45 +0100 |
commit | fab07978eca3bfcfa8ba43bce0e38f5340bffd8e (patch) | |
tree | a395b9920fab94d5ba67555640cf963fff6ddda1 /ltversion.m4 | |
parent | a402c3ac22ec70620d19a0758f10a8d15835fb5e (diff) | |
download | gdb-fab07978eca3bfcfa8ba43bce0e38f5340bffd8e.zip gdb-fab07978eca3bfcfa8ba43bce0e38f5340bffd8e.tar.gz gdb-fab07978eca3bfcfa8ba43bce0e38f5340bffd8e.tar.bz2 |
gdb/x86: move reading of cs and ds state into gdb/nat directory
This patch is part of a series that has the aim sharing the x86 Linux
target description creation code between GDB and gdbserver.
Within GDB part of this process involves reading the cs and ds state
from the 'struct user_regs_struct' using a ptrace call.
This isn't done by gdbserver, which is part of the motivation for this
whole series; the approach gdbserver takes is inferior to the approach
GDB takes (gdbserver relies on reading the file being debugged, and
extracting similar information from the file headers).
This commit moves the reading of cs and ds, which is used to figure
out if a thread is 32-bit or 64-bit (or in x32 mode), into the gdb/nat
directory so that the code can be shared with gdbserver, but at this
point I'm not actually using the code in gdbserver, that will come
later.
As such there should be no user visible changes after this commit, GDB
continues to do things as it did before (reading cs/ds), while
gdbserver continues to use its own approach (which doesn't require
reading cs/ds).
Approved-By: John Baldwin <jhb@FreeBSD.org>
Reviewed-By: Felix Willgerodt <felix.willgerodt@intel.com>
Diffstat (limited to 'ltversion.m4')
0 files changed, 0 insertions, 0 deletions