linux/kernel/debug/kdb/kdb_cmds

# Initial commands for kdb, alter to suit your needs.
# These commands are executed in kdb_init() context, no SMP, no
# processes.  Commands that require process data (including stack or
# registers) are not reliable this early.  set and bp commands should
# be safe.  Global breakpoint commands affect each cpu as it is booted.

# Standard debugging information for first level support, just type archkdb
# or archkdbcpu or archkdbshort at the kdb prompt.

defcmd dumpcommon "" "Common kdb debugging"
  set BTAPROMPT 0
  set LINES 10000
  -summary
  -cpu
  -ps
  -dmesg 600
  -bt
endefcmd

defcmd dumpall "" "First line debugging"
  set BTSYMARG 1
  set BTARGS 9
  pid R
  -dumpcommon
  -bta
endefcmd

defcmd dumpcpu "" "Same as dumpall but only tasks on cpus"
  set BTSYMARG 1
  set BTARGS 9
  pid R
  -dumpcommon
  -btc
endefcmd
kdb: core for kgdb back end (1 of 2) This patch contains only the kdb core. Because the change set was large, it was split. The next patch in the series includes the instrumentation into the core kernel which are mainly helper functions for kdb. This work is directly derived from kdb v4.4 found at: ftp://oss.sgi.com/projects/kdb/download/v4.4/ The kdb internals have been re-organized to make them mostly platform independent and to connect everything to the debug core which is used by gdbstub (which has long been known as kgdb). The original version of kdb was 58,000 lines worth of changes to support x86. From that implementation only the kdb shell, and basic commands for memory access, runcontrol, lsmod, and dmesg where carried forward. This is a generic implementation which aims to cover all the current architectures using the kgdb core: ppc, arm, x86, mips, sparc, sh and blackfin. More archictectures can be added by implementing the architecture specific kgdb functions. [mort@sgi.com: Compile fix with hugepages enabled] [mort@sgi.com: Clean breakpoint code renaming kdba_ -> kdb_] [mort@sgi.com: fix new line after printing registers] [mort@sgi.com: Remove the concept of global vs. local breakpoints] [mort@sgi.com: Rework kdb_si_swapinfo to use more generic name] [mort@sgi.com: fix the information dump macros, remove 'arch' from the names] [sfr@canb.auug.org.au: include fixup to include linux/slab.h] CC: linux-arch@vger.kernel.org Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Martin Hicks <mort@sgi.com> 2010-05-21 02:04:20 +00:00			`# Initial commands for kdb, alter to suit your needs.`
			`# These commands are executed in kdb_init() context, no SMP, no`
			`# processes. Commands that require process data (including stack or`
			`# registers) are not reliable this early. set and bp commands should`
			`# be safe. Global breakpoint commands affect each cpu as it is booted.`

			`# Standard debugging information for first level support, just type archkdb`
			`# or archkdbcpu or archkdbshort at the kdb prompt.`

			`defcmd dumpcommon "" "Common kdb debugging"`
			`set BTAPROMPT 0`
			`set LINES 10000`
			`-summary`
			`-cpu`
			`-ps`
			`-dmesg 600`
			`-bt`
			`endefcmd`

			`defcmd dumpall "" "First line debugging"`
			`set BTSYMARG 1`
			`set BTARGS 9`
			`pid R`
			`-dumpcommon`
			`-bta`
			`endefcmd`

			`defcmd dumpcpu "" "Same as dumpall but only tasks on cpus"`
			`set BTSYMARG 1`
			`set BTARGS 9`
			`pid R`
			`-dumpcommon`
			`-btc`
			`endefcmd`