#
267654 |
|
19-Jun-2014 |
gjb |
Copy stable/9 to releng/9.3 as part of the 9.3-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
235741 |
|
21-May-2012 |
jhb |
MFC 234190,234196,234280: - Extend the KDB interface to add a per-debugger callback to print a backtrace for an arbitrary thread (rather than the calling thread). A kdb_backtrace_thread() wrapper function uses the configured debugger if possible, otherwise it falls back to using stack(9) if that is available. - Replace a direct call to db_trace_thread() in propagate_priority() with a call to kdb_backtrace_thread() instead.
|
#
225736 |
|
22-Sep-2011 |
kensmith |
Copy head to stable/9 as part of 9.0-RELEASE release cycle.
Approved by: re (implicit)
|
#
183360 |
|
25-Sep-2008 |
jhb |
Initialize the DDB command list when initializing DDB so that the basic commands are available from 'boot -d'.
Suggested by: dfr
|
#
174914 |
|
26-Dec-2007 |
rwatson |
Add a simple scripting facility to DDB(4), allowing the user to define a set of named scripts. Each script consists of a list of DDB commands separated by ";"s that will be executed verbatim. No higher level language constructs, such as branching, are provided for: scripts are executed by sequentially injecting commands into the DDB input buffer.
Four new commands are present in DDB: "run" to run a specific script, "script" to define or print a script, "scripts" to list currently defined scripts, and "unscript" to delete a script, modeled on shell alias commands. Scripts may also be manipulated using sysctls in the debug.ddb.scripting MIB space, although users will prefer to use the soon-to-be-added ddb(8) tool for usability reasons.
Scripts with certain names are automatically executed on various DDB events, such as entering the debugger via a panic, a witness error, watchdog, breakpoint, sysctl, serial break, etc, allowing customized handling.
MFC after: 3 months
|
#
174910 |
|
25-Dec-2007 |
rwatson |
Add a new DDB(4) facility, output capture. Input and output from DDB may be captured to a memory buffer for later inspection using sysctl(8), or in the future, to a textdump.
A new DDB command, "capture", is added, which accepts arguments "on", "off", "reset", and "status".
A new DDB sysctl tree, debug.ddb.capture, is added, which can be used to resize the capture buffer and extract buffer contents.
MFC after: 3 months
|
#
164029 |
|
06-Nov-2006 |
kib |
Set up the context for the dbbe_trace callback in the ddb. Otherwise, trap caused by backtracing would lead to panic.
Noted and reviewed by: bde
|
#
139747 |
|
05-Jan-2005 |
imp |
Start each of the license/copyright comments with /*-
|
#
132791 |
|
28-Jul-2004 |
kan |
Damage control. Correcly advance symtab and strtab pointers, not table length values.
Spotted by: iedowse
|
#
132771 |
|
28-Jul-2004 |
kan |
Avoid casts as lvalues.
|
#
131952 |
|
10-Jul-2004 |
marcel |
Mega update for the KDB framework: turn DDB into a KDB backend. Most of the changes are a direct result of adding thread awareness. Typically, DDB_REGS is gone. All registers are taken from the trapframe and backtraces use the PCB based contexts. DDB_REGS was defined to be a trapframe on all platforms anyway. Thread awareness introduces the following new commands: thread X switch to thread X (where X is the TID), show threads list all threads.
The backtrace code has been made more flexible so that one can create backtraces for any thread by giving the thread ID as an argument to trace.
With this change, ia64 has support for breakpoints.
|