#
285830 |
|
23-Jul-2015 |
gjb |
- Copy stable/10@285827 to releng/10.2 in preparation for 10.2-RC1 builds. - Update newvers.sh to reflect RC1. - Update __FreeBSD_version to reflect 10.2. - Update default pkg(8) configuration to use the quarterly branch.[1]
Discussed with: re, portmgr [1] Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
234196 |
|
12-Apr-2012 |
jhb |
Update the ddb and gdb backends for the new 'trace_thread' hook. 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
|
#
218825 |
|
18-Feb-2011 |
mdf |
Modify kdb_trap() so that it re-calls the dbbe_trap function as long as 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
|
#
176651 |
|
29-Feb-2008 |
grehan |
Add support for kgdb's 'detach' command.
Reviewed by: marcel Sponsored by: Network Appliance
|
#
158949 |
|
26-May-2006 |
phk |
Don't use GDB_DBGPORT() macro to fill in dummy element in gdb_dbgport_set.
|
#
157059 |
|
23-Mar-2006 |
sam |
add support for copying console messages to a remote gdb
Reviewed by: kan
|
#
144245 |
|
28-Mar-2005 |
sam |
check return value of gdb_rx_varhex
Noticed by: Coverity Prevent analysis tool Reviewed by: kan
|
#
139778 |
|
06-Jan-2005 |
imp |
/* -> /*- for copyright notices, minor format tweaks as necessary
|
#
138253 |
|
01-Dec-2004 |
marcel |
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
|
#
133446 |
|
10-Aug-2004 |
marcel |
Comment-out the debugging printf I left in in case there were some packet related problems. No problems have been reported.
|
#
131899 |
|
10-Jul-2004 |
marcel |
Introduce the GDB debugger backend for the new KDB framework. The 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.
|