summaryrefslogtreecommitdiffstats
path: root/sys/kern/subr_kdb.c
Commit message (Collapse)AuthorAgeFilesLines
* /* -> /*- for copyright notices, minor format tweaks as necessaryimp2005-01-061-1/+1
|
* Zero terminate empty sting in kdb_sysctl_available.ups2004-10-211-0/+2
| | | | | Approved by: sam (mentor) MFC after: 1 week
* Fix a bug introduced in the previous commit: kdb_cpu_trap() gets tomarcel2004-09-261-1/+2
| | | | | | | | the trapframe via kdb_frame, but kdb_frame was not initialized until after the call to kdb_cpu_trap(). Ergo: kdb_cpu_trap() was moved too far up. Pointy hat: marcel
* Move makectx() after kdb_cpu_trap(), so the PCB will have possible MDmarcel2004-09-171-4/+4
| | | | corrections made to the trapframe. This is more logical.
* Make debug.kdb.stop_cpus also a TUNABLE() so it can be set prior to bootrwatson2004-08-221-0/+1
| | | | to help debug early nasty hangs.
* Add a new sysctl, debug.kdb.stop_cpus, which controls whether or not werwatson2004-08-151-2/+19
| | | | | | | | | | | attempt to IPI other cpus when entering the debugger in order to stop them while in the debugger. The default remains to issue the stop; however, that can result in a hang if another cpu has interrupts disabled and is spinning, since the IPI won't be received and the KDB will wait indefinitely. We probably need to add a timeout, but this is a useful stopgap in the mean time. Reviewed by: marcel
* Add kdb_thr_from_pid(), which given a PID returns the first threadmarcel2004-07-211-1/+15
| | | | in the process. This is useful when working from or with a process.
* Make kdb_dbbe_select() available as an interface function. This allowsmarcel2004-07-121-9/+20
| | | | | | changing the backend from outside the KDB frontend. For example from within a backend. Rewrite kdb_sysctl_current to make use of this function as well.
* Fix braino: Make sure there is a current backend before we return itsmarcel2004-07-111-2/+5
| | | | | | | name in the debug.kdb.current sysctl. All other dereferences are properly guarded, but this one was overlooked. Reported by: Morten Rodal (morten at rodal dot no)
* Introduce the KDB debugger frontend. The frontend provides a frameworkmarcel2004-07-101-0/+384
in which multiple (presumably different) debugger backends can be configured and which provides basic services to those backends. Besides providing services to backends, it also serves as the single point of contact for any and all code that wants to make use of the debugger functions, such as entering the debugger or handling of the alternate break sequence. For this purpose, the frontend has been made non-optional. All debugger requests are forwarded or handed over to the current backend, if applicable. Selection of the current backend is done by the debug.kdb.current sysctl. A list of configured backends can be obtained with the debug.kdb.available sysctl. One can enter the debugger by writing to the debug.kdb.enter sysctl.
OpenPOWER on IntegriCloud