Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add support for kgdb's 'detach' command. | grehan | 2008-02-29 | 1 | -0/+5 |
| | | | | | Reviewed by: marcel Sponsored by: Network Appliance | ||||
* | Don't use GDB_DBGPORT() macro to fill in dummy element in gdb_dbgport_set. | phk | 2006-05-26 | 1 | -1/+2 |
| | |||||
* | add support for copying console messages to a remote gdb | sam | 2006-03-23 | 1 | -2/+10 |
| | | | | Reviewed by: kan | ||||
* | check return value of gdb_rx_varhex | sam | 2005-03-28 | 1 | -2/+8 |
| | | | | | Noticed by: Coverity Prevent analysis tool Reviewed by: kan | ||||
* | /* -> /*- for copyright notices, minor format tweaks as necessary | imp | 2005-01-06 | 1 | -1/+1 |
| | |||||
* | Change gdb_cpu_setreg() to not take the value to which to set the | marcel | 2004-12-01 | 1 | -10/+24 |
| | | | | | | | | | | | | | | | | | | | | | 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 | ||||
* | Comment-out the debugging printf I left in in case there were some | marcel | 2004-08-10 | 1 | -1/+1 |
| | | | | packet related problems. No problems have been reported. | ||||
* | Introduce the GDB debugger backend for the new KDB framework. The | marcel | 2004-07-10 | 1 | -0/+261 |
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. |