Lines Matching full:using

2 Using kgdb, kdb and the kernel debugger internals
33 Two machines are required for using kgdb. One of these machines is a
71 If the architecture that you are using supports the kernel option
75 supports it for the architecture you are using, you can use hardware
106 ``CONFIG_KGDB_SERIAL_CONSOLE`` interface if you plan on using kdb on a
129 using kdb and kgdb as well as providing some examples of the
142 console as your primary console as well as using it to perform kernel
174 depending on if you are using kdb and/or kgdb, in one of the following
176 optional configurations together. Using kms + only gdb is generally not
179 Using loadable module or built-in
195    first is for an x86 target using the first serial port. The second
196    example is for the ARM Versatile AB using the second serial port.
225 depending on if you are using kdb and/or kgdb, in one of the following
265 When using kgdboc with no debugger proxy, you can end up connecting the
299 Kgdb supports using the gdb serial protocol to send console messages to
354 If the architecture that you are using enable KASLR by default,
360 Using kdb
368 1. Configure kgdboc at boot using kernel parameters::
374    Configure kgdboc after the kernel has booted; assuming you are using
381    manually; all involve using the :kbd:`SysRq-G`, which means you must have
388    -  Example using minicom 2.2
411    ``bt``      Get a backtrace of the current process using :c:func:`dump_stack`
416 4. When you are done using kdb you need to consider rebooting the system
417    or using the ``go`` command to resuming normal kernel execution. If you
421    consideration when using the kernel debugger.
423 Quick start for kdb using a keyboard connected console
428 1. Configure kgdboc at boot using kernel parameters::
440    manually; all involve using the :kbd:`SysRq-G`, which means you must have
447    -  Example using a laptop keyboard:
461    -  Example using a PS/2 101-key keyboard
474 Using kgdb / gdb
497    Configure kgdboc at boot using kernel parameters::
511    using kgdbwait as a boot argument, via a :kbd:`SysRq-G`, or running the
519    -  Example using minicom 2.2
534    Example (using a directly connected port)::
619 It is possible to run a limited set of kdb commands from gdb, using the
622 debugger. You should be using gdb for breakpoints and run control
682       using the debugger
824 When using kgdboc with a UART, the UART driver must implement two
861 switch to a text context when you are using ``kgdboc=kms,kbd``, provided