diff options
author | marcel <marcel@FreeBSD.org> | 2004-12-01 06:40:35 +0000 |
---|---|---|
committer | marcel <marcel@FreeBSD.org> | 2004-12-01 06:40:35 +0000 |
commit | c106bd9120d0e0d75dc9a28f87686d6b6d18ae8c (patch) | |
tree | 62c9a95681df36f1242efe2fd847059217302039 /sys/compat | |
parent | ff42094303dbb28e905ab1bee9975ca994fea668 (diff) | |
download | FreeBSD-src-c106bd9120d0e0d75dc9a28f87686d6b6d18ae8c.zip FreeBSD-src-c106bd9120d0e0d75dc9a28f87686d6b6d18ae8c.tar.gz |
Change gdb_cpu_setreg() to not take the value to which to set the
specified register, but a pointer to the in-memory representation of
that value. The reason for this is twofold:
1. Not all registers can be represented by a register_t. In particular
FP registers fall in that category. Passing the new register value
by reference instead of by value makes this point moot.
2. When we receive a G or P packet, both are for writing a register,
the packet will have the register value in target-byte order and
in the memory representation (modulo the fact that bytes are sent
as 2 printable hexadecimal numbers of course). We only need to
decode the packet to have a pointer to the register value.
This change fixes the bug of extracting the register value of the P
packet as a hexadecimal number instead of as a bit array. The quick
(and dirty) fix to bswap the register value in gdb_cpu_setreg() as
it has been added on i386 and amd64 can therefore be removed and has
in fact been that.
Tested on: alpha, amd64, i386, ia64, sparc64
Diffstat (limited to 'sys/compat')
0 files changed, 0 insertions, 0 deletions