[ Bottom of Page | Previous Page | Next Page | Contents | Index | Library Home | Legal | Search ]

Kernel Extensions and Device Support Programming Concepts

Miscellaneous Subcommands

time and debug Subcommands

The time command can be used to determine the elapsed time from the last time the KDB Kernel Debugger was left to the time it was entered.

The debug subcommand may be used to print additional information during KDB execution, the primary use of this subcommand is to aid in ensuring that the debugger is functioning properly. If invoked with no arguments the currently active debug options are displayed.

Note
The time subcommand is only available within the KDB Kernel Debugger, it is not included in the kdb command.
Syntax

 

time

debug [?]

Example
   KDB(4)> debug ? debug help
   vmm HW lookup debug... on with arg 'dbg1++', off with arg 'dbg1--'
   vmm tr/tv cmd debug... on with arg 'dbg2++', off with arg 'dbg2--'
   vmm SW lookup debug... on with arg 'dbg3++', off with arg 'dbg3--'
   symbol lookup debug... on with arg 'dbg4++', off with arg 'dbg4--'
   stack trace debug..... on with arg 'dbg5++', off with arg 'dbg5--'
   BRKPT debug (list).... on with arg 'dbg61++', off with arg 'dbg61--'
   BRKPT debug (instr)... on with arg 'dbg62++', off with arg 'dbg62--'
   BRKPT debug (suspend). on with arg 'dbg63++', off with arg 'dbg63--'
   BRKPT debug (phantom). on with arg 'dbg64++', off with arg 'dbg64--'
   BRKPT debug (context). on with arg 'dbg65++', off with arg 'dbg65--'
   DABR debug (address).. on with arg 'dbg71++', off with arg 'dbg71--'
   DABR debug (register). on with arg 'dbg72++', off with arg 'dbg72--'
   DABR debug (status)... on with arg 'dbg73++', off with arg 'dbg73--'
   BRAT debug (address).. on with arg 'dbg81++', off with arg 'dbg81--'
   BRAT debug (register). on with arg 'dbg82++', off with arg 'dbg82--'
   BRAT debug (status)... on with arg 'dbg83++', off with arg 'dbg83--'
   BRKPT debug (context). on this debug feature is enable
   KDB(4)> debug dbg5++ enable debug mode
   stack trace debug..... on
   KDB(4)> f stack frame in debug mode
   thread+000180 STACK:
   === Look for traceback at 0x00015278
   === Got traceback at 0x00015280 (delta = 0x00000008)
   === has_tboff = 1, tb_off = 0xD8
   === Trying to find Stack Update Code from 0x000151A8 to 0x00015278
   === Found 0x9421FFA0 at 0x000151B8
   === Trying to find Stack Restore Code from 0x000151A8 to 0x0001527C
   === Trying to find Registers Save Code from 0x000151A8 to 0x00015278
   [00015278]waitproc+0000D0 ()
   === Look for traceback at 0x00015274
   === Got traceback at 0x00015280 (delta = 0x0000000C)
   === has_tboff = 1, tb_off = 0xD8
   [00015274]waitproc+0000CC ()
   === Look for traceback at 0x0002F400
   === Got traceback at 0x0002F420 (delta = 0x00000020)
   === has_tboff = 1, tb_off = 0x30
   [0002F400]procentry+000010 (??, ??, ??, ??)

   /# ls   Invoke command from command line that calls open
   Breakpoint
   0024FDE8     stwu   stkp,FFFFFFB0(stkp) stkp=2FF3B3C0,FFFFFFB0(stkp)=2FF3B370
   KDB(0)> time  Report time from leaving the debugger till the break
   Command: time  Aliases:   
   Elapsed time since last leaving the debugger:
   2 seconds and 121211136 nanoseconds.
   KDB(0)>

reboot Subcommand

The reboot subcommand can be used to reboot the machine. This subcommand issues a prompt for confirmation that a reboot is desired before executing the reboot. If the reboot request is confirmed, the soft reboot interface is called (sr_slih(1)).

Note
This subcommand is only available within the KDB Kernel Debugger, it is not included in the kdb command.
Syntax

 

reboot

Example
   KDB(0)> reboot reboot the machine
   Do you want to continue system reboot? (y/[n]):> y
   Rebooting ...

[ Top of Page | Previous Page | Next Page | Contents | Index | Library Home | Legal | Search ]