KDB - Revision history

Tim Bird: /* Config variables */

2011-12-19T17:57:24Z

‎Config variables

2011-10-27T09:56:49Z

2011-09-20T16:32:07Z

‎Config variables: move CONFIG_DEBUG_RODATA=n to mandatory config variable section

2011-07-20T23:29:28Z

‎Feature extension notes (by Tim)

2011-07-20T17:50:58Z

‎Kernel configuration

2011-07-05T23:45:06Z

‎Feature extension notes (by Tim): add notes about my notes

2011-07-05T23:40:48Z

‎Kernel configuration: DEBUG_RODATA can be used with software breakpoints as well

2011-06-30T21:54:39Z

‎Feature extension notes (by Tim)

2011-06-30T21:53:50Z

‎internals

2011-06-30T21:34:09Z

‎At boot time (via kernel command line)

@@ Line 46: / Line 46: @@
 ** Sysrq-g must be used to break in initially.
 ** Selecting this will automatically set:
-*** CONFIG_CONSOLE_POLL=N
+*** CONFIG_CONSOLE_POLL=Y
 *** CONFIG_MAGIC_SYSRQ=Y - turn on MAGIC-SYSRQ key support
 * CONFIG_KGDB_KDB=Y - actually turn on the KDB debugger feature

← Older revision		Revision as of 09:56, 27 October 2011
Line 289:		Line 289:
	* kdbgetenv()		* kdbgetenv()
	* kdbgetulenv() - get unsigned long env variable		* kdbgetulenv() - get unsigned long env variable
		+
		+	[[Category:Development Tools]]

@@ Line 49: / Line 49: @@
 *** CONFIG_MAGIC_SYSRQ=Y - turn on MAGIC-SYSRQ key support
 * CONFIG_KGDB_KDB=Y - actually turn on the KDB debugger feature
 Optional other configuration settings:
 * CONFIG_FRAME_POINTER=Y - this allows for better backtrace support in KDB
 * CONFIG_KALLSYMS=Y - this adds symbolic information to the kernel, useful to see symbols instead of addresses
 * CONFIG_KDB_KEYBOARD - use KDB with an attached keyboard (not for use with serial console)

@@ Line 278: / Line 278: @@
 * Can break on __do_user_fault, to break into kdb on user process SIGSEGV (on ARM, anyway)
-* See CONFIG_DEBUG_USER (on ARM) for extra information shown and code paths used, on user-space on faults
+* See CONFIG_DEBUG_USER (on ARM) for extra information shown and code paths used, on user-space faults
 * I can't set a breakpoint from kdb_cmds (on kdb initialization)

@@ Line 40: / Line 40: @@
 In order to support KDB, "KGDB" support must be turned on first (even if you aren't using kgdb/gdb)
 * CONFIG_DEBUG_KERNEL=Y - includes debug information in the kernel compilation - required for basic kernel debugging support
 * CONFIG_KGDB=Y - turn on basic kernel debug agent support
@@ Line 55: / Line 56: @@
 * CONFIG_KDB_KEYBOARD - use KDB with an attached keyboard (not for use with serial console)
 * CONFIG_KGDB_TESTS - used to turn on kgdb internal self-tests - see the config help for this for more information
 == Enabling kdb ==

@@ Line 254: / Line 254: @@
 == Feature extension notes (by Tim) ==
 * Can break on __do_user_fault, to break into kdb on user process SIGSEGV (on ARM, anyway)
 * See CONFIG_DEBUG_USER (on ARM) for extra information shown and code paths used, on user-space on faults
 * I can't set a breakpoint from kdb_cmds (on kdb initialization)
-** I get any breakpoint set on kdb initialization
+** I get a hang (likely a panic before the console starts) on any breakpoint set on kdb initialization
 === internals ===

@@ Line 253: / Line 253: @@
 If you hit <enter> without typing a command, sometimes (when it makes sense) the last command run will be run again.  For 'md' commands, the next command will continue at the address where the last command left off.
-== internals ==
+== Feature extension notes (by Tim) ==
 internal functions to retrieve environment variables:
 * kdbgetintenv()
 * kdbgetenv()
 * kdbgetulenv() - get unsigned long env variable

@@ Line 73: / Line 73: @@
 kernel command line.  Normally, you specify the tty device name, followed by the serial port speed.
-  $ kgdboc=ttyS0,115200
+  kgdboc=ttyS0,115200
-−
 == Invoking kdb ==