Invoking the debugger

You can invoke the debugger in any of the following ways:

• On SVR5, issue the kdb command on the command line. The ``current'' debugger is invoked. Issue the newdebug command to toggle between kdb and scodb if both are linked into the kernel. The kdb prompt is kdb>>; the scodb prompt is debug:0:0.

  On SCO OpenServer 5, issue the scodb command on the command line.

• Run a program on a SVR5 system that calls the sysi86(SI86TODEMON) system call.

• Execute a DDI driver that uses the call_demon(D3) function or an ODDI driver that uses the calldebug(D3oddi) function.

• On SVR5, press <Ctrl><Alt><D> (from the console only) on an AT-bus system, or type the interrupt character (from the console only) on a Multibus system.

  On SCO OpenServer 5 systems, the character sequence for invoking the debugger is configurable; by default, it is <Ctrl><X>.

• The kernel debugger is entered automatically under various conditions, such as panics and breakpoint traps. Any time the kdb>> or debug:0:0 prompt appears, you are in the debugger. I/O is performed through the console or a serial terminal.

• To exit the debugger on SVR5, press <Ctrl>-<D> or <q>. To exit the debugger on SCO OpenServer 5, press <q>.

When you exit and re-enter the debugger, its state is preserved, including the contents of the kdb value stack.