summaryrefslogtreecommitdiffstats
path: root/sys/gdb/gdb_main.c
Commit message (Collapse)AuthorAgeFilesLines
* Add support for gdb's memory searching capabilities to our in-kernel gdbbenno2014-09-051-0/+24
| | | | | | | | server. Submitted by: Daniel O'Connor <daniel.oconnor@isilon.com> Reviewed by: jhb Sponsored by: EMC Isilon Storage Division
* Update the ddb and gdb backends for the new 'trace_thread' hook.jhb2012-04-121-1/+1
| | | | | | | | | It is implemented via db_trace_thread() for DDB and not implemented for GDB. This should have been part of r234190. Pointy hat to: jhb Reported by: jkim MFC after: 1 week
* Modify kdb_trap() so that it re-calls the dbbe_trap function as long asmdf2011-02-181-0/+11
| | | | | | | | | | | | | | | the debugger back-end has changed. This means that switching from ddb to gdb no longer requires a "step" which can be dangerous on an already-crashed kernel. Also add a capability to get from the gdb back-end back to ddb, by typing ^C in the console window. While here, simplify kdb_sysctl_available() by using sbuf_new_for_sysctl(), and use strlcpy() instead of strncpy() since the strlcpy semantic is desired. MFC after: 1 month
* Add support for kgdb's 'detach' command.grehan2008-02-291-0/+5
| | | | | Reviewed by: marcel Sponsored by: Network Appliance
* Don't use GDB_DBGPORT() macro to fill in dummy element in gdb_dbgport_set.phk2006-05-261-1/+2
|
* add support for copying console messages to a remote gdbsam2006-03-231-2/+10
| | | | Reviewed by: kan
* check return value of gdb_rx_varhexsam2005-03-281-2/+8
| | | | | Noticed by: Coverity Prevent analysis tool Reviewed by: kan
* /* -> /*- for copyright notices, minor format tweaks as necessaryimp2005-01-061-1/+1
|
* Change gdb_cpu_setreg() to not take the value to which to set themarcel2004-12-011-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 somemarcel2004-08-101-1/+1
| | | | packet related problems. No problems have been reported.
* Introduce the GDB debugger backend for the new KDB framework. Themarcel2004-07-101-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.
OpenPOWER on IntegriCloud