summaryrefslogtreecommitdiffstats
path: root/sys/gdb
Commit message (Collapse)AuthorAgeFilesLines
* kern cons: introduce infrastructure for console grabbing by kernelavg2011-12-171-0/+10
| | | | | | | | | | | | At the moment grab and ungrab methods of all console drivers are no-ops. Current intended meaning of the calls is that the kernel takes control of console input. In the future the semantics may be extended to mean that the calling thread takes full ownership of the console (e.g. console output from other threads could be suspended). Inspired by: bde MFC after: 2 months
* Modify kdb_trap() so that it re-calls the dbbe_trap function as long asmdf2011-02-182-0/+23
| | | | | | | | | | | | | | | 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
* there must be only one SYSINIT with SI_SUB_RUN_SCHEDULER+SI_ORDER_ANY orderavg2010-09-301-1/+1
| | | | | | | | | | | | | | | SI_SUB_RUN_SCHEDULER+SI_ORDER_ANY should only be used to call scheduler() function which turns the initial thread into swapper proper and thus there is no further SYSINIT processing. Other SYSINITs with SI_SUB_RUN_SCHEDULER+SI_ORDER_ANY may get ordered after scheduler() and thus never executed. That particular relative order is semi-arbitrary. Thus, change such places to use SI_ORDER_MIDDLE. Also, use SI_ORDER_MIDDLE instead of correct, but less appealing, SI_ORDER_ANY - 1. MFC after: 1 week
* Commit SYSINIT() ;-adding patch missed in previous pass.rwatson2008-03-161-1/+1
| | | | | MFC after: 1 month Caught by: tinderbox
* Add support for kgdb's 'detach' command.grehan2008-02-291-0/+5
| | | | | Reviewed by: marcel Sponsored by: Network Appliance
* Add kdb_cpu_sync_icache(), intended to synchronize instructionmarcel2007-06-091-2/+8
| | | | | | caches with data caches after writing to memory. This typically is required to make breakpoints work on ia64 and powerpc. For those architectures the function is implemented.
* Convert to new console apiphk2006-05-261-4/+7
|
* Eliminate gdb_checkc member from GDB_DBGPORT(), it is never used.phk2006-05-261-6/+4
| | | | | Use polling behaviour for gdb_getc() where convenient, this edges us closer to the console code.
* Don't use GDB_DBGPORT() macro to fill in dummy element in gdb_dbgport_set.phk2006-05-261-1/+2
|
* Wrap our drivers gdb_getc() function so that if it returns -1 wephk2006-05-261-5/+20
| | | | | try again. This way it matches the console behaviour and allows us to share more code.
* add support for copying console messages to a remote gdbsam2006-03-233-2/+185
| | | | 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-064-4/+4
|
* 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-104-0/+721
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