Documentation/dev-tools/kgdb.rst

2 Using kgdb, kdb and the kernel debugger internals
33 Two machines are required for using kgdb. One of these machines is a
70 If the architecture that you are using supports the kernel option
74 supports it for the architecture you are using, you can use hardware
105 ``CONFIG_KGDB_SERIAL_CONSOLE`` interface if you plan on using kdb on a
128 using kdb and kgdb as well as providing some examples of the
141 console as your primary console as well as using it to perform kernel
173 depending on if you are using kdb and/or kgdb, in one of the following
175 optional configurations together. Using kms + only gdb is generally not
178 Using loadable module or built-in
194    first is for an x86 target using the first serial port. The second
195    example is for the ARM Versatile AB using the second serial port.
224 depending on if you are using kdb and/or kgdb, in one of the following
264 When using kgdboc with no debugger proxy, you can end up connecting the
282 to work using the boot console until it can transition to the regular
322 Kgdb supports using the gdb serial protocol to send console messages to
377 If the architecture that you are using enable KASLR by default,
383 Using kdb
391 1. Configure kgdboc at boot using kernel parameters::
397    Configure kgdboc after the kernel has booted; assuming you are using
404    manually; all involve using the :kbd:`SysRq-G`, which means you must have
411    -  Example using minicom 2.2
434    ``bt``      Get a backtrace of the current process using dump_stack()
439 4. When you are done using kdb you need to consider rebooting the system
440    or using the ``go`` command to resuming normal kernel execution. If you
444    consideration when using the kernel debugger.
446 Quick start for kdb using a keyboard connected console
451 1. Configure kgdboc at boot using kernel parameters::
463    manually; all involve using the :kbd:`SysRq-G`, which means you must have
470    -  Example using a laptop keyboard:
484    -  Example using a PS/2 101-key keyboard
497 Using kgdb / gdb
520    Configure kgdboc at boot using kernel parameters::
534    using kgdbwait as a boot argument, via a :kbd:`SysRq-G`, or running the
542    -  Example using minicom 2.2
557    Example (using a directly connected port)::
642 It is possible to run a limited set of kdb commands from gdb, using the
645 debugger. You should be using gdb for breakpoints and run control
705       using the debugger
847 When using kgdboc with a UART, the UART driver must implement two
884 switch to a text context when you are using ``kgdboc=kms,kbd``, provided