diff options
| author | Nathan Froyd <froydnj@codesourcery.com> | 2009-06-04 19:02:28 -0700 |
|---|---|---|
| committer | Aurelien Jarno <aurelien@aurel32.net> | 2009-07-12 23:42:05 +0200 |
| commit | 22555301adabad6ef2401a7f02bfc2337044ddbd (patch) | |
| tree | 6b846416854416146d0c7e12d58fb4aec14a0066 /gdb-xml/power64-core.xml | |
| parent | 33890b3e0deb8891d5b1241671eb3979f8896bf3 (diff) | |
| download | qemu-22555301adabad6ef2401a7f02bfc2337044ddbd.tar.gz | |
gdb-xml: fix hacks in powerpc register numbering
The powerpc xml files contained a hack--an empty, non-existent
register--for getting the register numbers to line up for
newer (XML-aware) and older (non-XML-aware) GDB. While this hack worked
in some cases, it didn't work in all cases, notably when the user used
`finish' or `continue': GDB would attempt to read the non-existent
register and QEMU would complain.
This patch fixes things up properly. Instead of inserting a fake
register, we explicitly declare the floating-point and SPE registers to
start at 71. This action accomplishes the same thing as the nasty hack,
except that now GDB never tries to fetch the non-existant register 70.
Signed-off-by: Nathan Froyd <froydnj@codesourcery.com>
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Diffstat (limited to 'gdb-xml/power64-core.xml')
| -rw-r--r-- | gdb-xml/power64-core.xml | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/gdb-xml/power64-core.xml b/gdb-xml/power64-core.xml index fef42e4166..6cc1531201 100644 --- a/gdb-xml/power64-core.xml +++ b/gdb-xml/power64-core.xml @@ -46,13 +46,4 @@ <reg name="lr" bitsize="64" type="code_ptr"/> <reg name="ctr" bitsize="64" type="uint64"/> <reg name="xer" bitsize="32" type="uint32"/> - <!-- HACK: The way the QEMU GDB stub code is currently written requires - the "integer" registers from the XML file to span the entirety of - NUM_CORE_REGS that non-XML-aware GDB requires. Otherwise, XML-aware - GDB thinks that "coprocessor" registers from XML, such as the - floating-point registers, have register numbers less than - NUM_CORE_REGS. This can lead to problems. Work around it by using - an unnamed register as padding; NUM_CORE_REGS on Power is 71 and - this register is 70. It would be fpscr for non-XML-aware GDB. --> - <reg name="" bitsize="32" type="uint32"/> </feature> |