Documentation/dev-tools/kgdb.rst

2 Using kgdb, kdb and the kernel debugger internals
10 The kernel has two different debugger front ends (kdb and kgdb) which
12 debugger front ends and dynamically transition between them if you
18 stop in a certain location. Kdb is not a source level debugger, although
25 Kgdb is intended to be used as a source level debugger for the Linux
56 :menuselection:`KGDB: kernel debugger`.
67 or on the stack at different points which allows a debugger such as gdb to
123 Kernel Debugger Boot Arguments
127 the configuration of the kernel debugger. The following chapter covers
150 that has atomic mode setting hooks, it is possible to enter the debugger
260    separate TCP port for the debugger and a separate TCP port for the
264 When using kgdboc with no debugger proxy, you can end up connecting the
265 debugger at one of two entry points. If an exception occurs after you
267 waiting for the debugger. In this case you disconnect your terminal
268 program and then connect the debugger in its place. If you want to
273 on the initial connect, or to use a debugger proxy that allows an
304 debugger connection during booting of a kernel. You can only use this
323 the debugger when the debugger is connected and running. There are two
353 The kgdbreboot feature allows you to change how the debugger deals with
368     - Send the detach message to any attached debugger client.
372     - Enter the debugger on reboot notify.
402 2. Enter the kernel debugger manually or by waiting for an oops or
403    fault. There are several ways you can enter the kernel debugger
444    consideration when using the kernel debugger.
461 2. Enter the kernel debugger manually or by waiting for an oops or
462    fault. There are several ways you can enter the kernel debugger
511 configuration while the debugger is attached. Make sure to detach the
512 debugger with the ``detach`` command prior to trying to unconfigure a
530 2. Stop kernel execution (break into the debugger)
535    kernel until it takes an exception where it waits for the debugger to
583 shell or script to break into the debugger.
600 Whenever the kernel debugger stops in kgdb mode it will print the
645 debugger. You should be using gdb for breakpoints and run control
684 Kernel Debugger Internals
690 The kernel debugger is organized into a number of components:
694    The debug core is found in ``kernel/debugger/debug_core.c``. It
705       using the debugger
747    The kdb debugger shell is broken down into a number of components.
843 atomic context. When kgdb makes an I/O request to the debugger, kgdboc
863 debugger detaches. You need to be very careful with any kind of lock you
888 Every time the kernel debugger is entered it calls
891 debugger calls kgdboc_post_exp_handler() which in turn calls
894 Any video driver that wants to be compatible with the kernel debugger