Lines Matching +full:broken +full:- +full:turn +full:- +full:around
15 Kdb is simplistic shell-style interface which you can use on a system
22 kernel built-ins or in kernel modules if the code was built with
40 kgdb I/O modules compiled as built-ins or loadable kernel modules in the
46 - In order to enable compilation of kdb, you must first enable kgdb.
48 - The kgdb test compile options are described in the kgdb test suite
52 ------------------------------
55 :menuselection:`Kernel hacking --> Kernel debugging` and select
60 will want to turn on ``CONFIG_DEBUG_INFO`` which is called
63 It is advised, but not required, that you turn on the
74 certain regions of the kernel's memory space as read-only. If kgdb
77 option turned on, else you need to turn off this option.
94 -----------------------------
109 If you want to use a PS/2-style keyboard with kdb, you would select
133 ------------------------
145 built-in or a kernel loadable module. You can only make use of
147 a built-in.
169 - kms = Kernel Mode Setting
171 - kbd = Keyboard
179 Using loadable module or built-in
182 1. As a kernel built-in:
186 kgdboc=<tty-device>,[baud]
192 modprobe kgdboc kgdboc=<tty-device>,[baud]
259 protocol. You must manually send a :kbd:`SysRq-G` unless you have a proxy
262 "human" console. The proxy can take care of sending the :kbd:`SysRq-G`
273 don't like this are to hack gdb to send the :kbd:`SysRq-G` for you as well as
278 -------------------------------------
302 ------------------------------
317 -----------------------------
352 ----------------------------------
360 .. flat-table::
363 * - 1
364 - ``echo -1 > /sys/module/debug_core/parameters/kgdbreboot``
365 - Ignore the reboot notification entirely.
367 * - 2
368 - ``echo 0 > /sys/module/debug_core/parameters/kgdbreboot``
369 - Send the detach message to any attached debugger client.
371 * - 3
372 - ``echo 1 > /sys/module/debug_core/parameters/kgdbreboot``
373 - Enter the debugger on reboot notify.
376 -----------------------------
388 ------------------------------------
405 manually; all involve using the :kbd:`SysRq-G`, which means you must have
408 - When logged in as root or with a super user session you can run::
410 echo g > /proc/sysrq-trigger
412 - Example using minicom 2.2
414 Press: :kbd:`CTRL-A` :kbd:`f` :kbd:`g`
416 - When you have telneted to a terminal server that supports sending
419 Press: :kbd:`CTRL-]`
448 ------------------------------------------------------
464 manually; all involve using the :kbd:`SysRq-G`, which means you must have
467 - When logged in as root or with a super user session you can run::
469 echo g > /proc/sysrq-trigger
471 - Example using a laptop keyboard:
485 - Example using a PS/2 101-key keyboard
517 ------------------------------------
535 using kgdbwait as a boot argument, via a :kbd:`SysRq-G`, or running the
539 - When logged in as root or with a super user session you can run::
541 echo g > /proc/sysrq-trigger
543 - Example using minicom 2.2
545 Press: :kbd:`CTRL-A` :kbd:`f` :kbd:`g`
547 - When you have telneted to a terminal server that supports sending
550 Press: :kbd:`CTRL-]`
582 to issue an other :kbd:`SysRq-G`. It is easy to create a simple entry point by
594 ------------------------------
616 Now you must kill gdb. Typically you press :kbd:`CTRL-Z` and issue
619 kill -9 %
641 -----------------------------
689 ----------------------
698 - A generic OS exception handler which includes sync'ing the
699 processors into a stopped state on an multi-CPU system.
701 - The API to talk to the kgdb I/O drivers
703 - The API to make calls to the arch-specific kgdb implementation
705 - The logic to perform safe memory reads and writes to memory while
708 - A full implementation for software breakpoints unless overridden
711 - The API to invoke either the kdb or kgdb frontend to the debug
714 - The structures and callback API for atomic kernel mode setting.
718 2. kgdb arch-specific implementation
724 The arch-specific portion implements:
726 - contains an arch-specific trap catcher which invokes
729 - translation to and from gdb specific packet format to struct pt_regs
731 - Registration and unregistration of architecture specific trap
734 - Any special exception handling and cleanup
736 - NMI exception handling and cleanup
738 - (optional) HW breakpoints
744 - All the logic to implement the gdb serial protocol
748 The kdb debugger shell is broken down into a number of components.
755 - A simple shell
757 - The kdb core command set
759 - A registration API to register additional kdb shell commands.
761 - A good example of a self-contained kdb module is the ``ftdump``
765 - For an example of how to dynamically register a new kdb command
772 - The implementation for kdb_printf() which emits messages directly
775 - SW / HW breakpoint management for the kdb shell
782 - configuration via built-in or module
784 - dynamic configuration and kgdb hook registration calls
786 - read and write character interface
788 - A cleanup handler for unconfiguring from the kgdb core
790 - (optional) Early debug methodology
810 - ``NUMREGBYTES``:
814 - ``BUFMAX``:
818 - ``CACHE_FLUSH_IS_SAFE``:
825 ``kernel/kgdb.c``, that must be supplied by the architecture-specific
830 .. kernel-doc:: include/linux/kgdb.h
834 ----------------
845 invokes a callback in the serial core which in turn uses the callback in
859 Any implementation specifics around creating a polling driver use the
878 :c:expr:`kdb_poll_funcs[]`. The kdb_get_kbd_char() is the top-level
890 kgdboc_pre_exp_handler() which in turn calls con_debug_enter()
892 debugger calls kgdboc_post_exp_handler() which in turn calls
936 - Jason Wessel <jason.wessel@windriver.com>
940 - Jason Wessel <jason.wessel@windriver.com>