summaryrefslogtreecommitdiff
path: root/gdb/gdbcore.h
diff options
context:
space:
mode:
authorJason Molenda <jsm@bugshack.cygnus.com>1999-12-08 02:51:13 +0000
committerJason Molenda <jsm@bugshack.cygnus.com>1999-12-08 02:51:13 +0000
commitbcfcec8b9d97083bc5786b31fccd7eba4c70106a (patch)
treef85313f9823b766f0047050818505ce694ac428d /gdb/gdbcore.h
parent96047344dc24efb4bbddb0b2bd8d3b2d4e2be802 (diff)
downloadgdb-bcfcec8b9d97083bc5786b31fccd7eba4c70106a.tar.gz
import gdb-1999-12-07 snapshot
Diffstat (limited to 'gdb/gdbcore.h')
-rw-r--r--gdb/gdbcore.h12
1 files changed, 9 insertions, 3 deletions
diff --git a/gdb/gdbcore.h b/gdb/gdbcore.h
index 0db61f992d7..e8e395384f9 100644
--- a/gdb/gdbcore.h
+++ b/gdb/gdbcore.h
@@ -163,15 +163,21 @@ struct core_fns
CORE_REG_SIZE is the size of that area.
- WHICH says which set of registers we are handling (0 = int, 2 = float on
- machines where they are discontiguous).
+ WHICH says which set of registers we are handling:
+ 0 --- integer registers
+ 2 --- floating-point registers, on machines where they are
+ discontiguous
+ 3 --- extended floating-point registers, on machines where
+ these are present in yet a third area. (GNU/Linux uses
+ this to get at the SSE registers.)
REG_ADDR is the offset from u.u_ar0 to the register values relative to
core_reg_sect. This is used with old-fashioned core files to locate the
registers in a large upage-plus-stack ".reg" section. Original upage
address X is at location core_reg_sect+x+reg_addr. */
- void (*core_read_registers) PARAMS ((char *core_reg_sect, unsigned core_reg_size,
+ void (*core_read_registers) PARAMS ((char *core_reg_sect,
+ unsigned core_reg_size,
int which, CORE_ADDR reg_addr));
/* Finds the next struct core_fns. They are allocated and initialized