Marcel Moolenaar cbc174356c Introduce the KDB debugger frontend. The frontend provides a framework ... 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.		2004-07-10 18:40:12 +00:00
..
alpha	Introduce the GDB debugger backend for the new KDB framework. The	2004-07-10 17:47:22 +00:00
compile
conf	Add option GEOM_GPT. This brings the ability to have a large number of	2004-05-02 20:40:19 +00:00
include	Introduce the KDB debugger frontend. The frontend provides a framework	2004-07-10 18:40:12 +00:00
isa	Catch up with __RMAN_RESOURCE_VISIBLE enough to get GENERIC to build	2004-07-01 15:07:27 +00:00
linux	Regenerate.	2004-06-04 13:52:51 +00:00
mcbus	Catch up with __RMAN_RESOURCE_VISIBLE enough to get GENERIC to build	2004-07-01 15:07:27 +00:00
osf1	- Replace wait1() with a kern_wait() function that accepts the pid,	2004-03-17 20:00:00 +00:00
pci	Catch up with __RMAN_RESOURCE_VISIBLE enough to get GENERIC to build	2004-07-01 15:07:27 +00:00
tlsb	Catch up with __RMAN_RESOURCE_VISIBLE enough to get GENERIC to build	2004-07-01 15:07:27 +00:00
Makefile