summaryrefslogtreecommitdiffstats
path: root/sys/amd64/include/gdb_machdep.h
Commit message (Collapse)AuthorAgeFilesLines
* Change GDB_BUFSZ to be large enough to hold a register dump where eachjhb2007-02-051-1/+1
| | | | | | | | | | | register takes 16 characters (64-bit register in hex). In practice this is a slight bit of overkill as 7 of the 56 registers are only 32-bit, but having the buffer too small results in remote kgdb trashing kernel memory when it connects. PR: amd64/108673 Submitted by: Ravi Murty, Nikhil Rao @ Intel MFC after: 3 days
* Sync with i386: Map exceptions to signals in gdb_cpu_signal() somarcel2006-04-041-6/+1
| | | | | | that kgdb(1) gets a SIGTRAP when it needs to. Pointed out by: grehan@
* The PC is register 16, not 18.marcel2006-04-041-1/+1
| | | | Pointed out by: grehan@
* Begin all license/copyright comments with /*-imp2005-01-051-1/+1
|
* Change gdb_cpu_setreg() to not take the value to which to set themarcel2004-12-011-1/+1
| | | | | | | | | | | | | | | | | | | | | 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
* Introduce the GDB debugger backend for the new KDB framework. Themarcel2004-07-101-0/+57
backend improves over the old GDB support in the following ways: o Unified implementation with minimal MD code. o A simple interface for devices to register themselves as debug ports, ala consoles. o Compression by using run-length encoding. o Implements GDB threading support.
OpenPOWER on IntegriCloud