Lines Matching refs:you
12 debugger front ends and dynamically transition between them if you
15 Kdb is simplistic shell-style interface which you can use on a system
19 you can set breakpoints and execute some basic kernel run control. Kdb
46 - In order to enable compilation of kdb, you must first enable kgdb.
54 To enable ``CONFIG_KGDB`` you should look under
58 While it is not a hard requirement that you have symbols in your vmlinux
59 file, gdb tends not to be very useful without the symbolic data, so you
63 It is advised, but not required, that you turn on the
71 If the architecture that you are using supports the kernel option
72 ``CONFIG_STRICT_KERNEL_RWX``, you should consider turning it off. This
75 supports it for the architecture you are using, you can use hardware
76 breakpoints if you desire to run with the ``CONFIG_STRICT_KERNEL_RWX``
77 option turned on, else you need to turn off this option.
79 Next you should choose one of more I/O drivers to interconnect debugging
83 kernel or module parameters which you can learn more about in the in the
99 printing out interesting data such as what you would see if you ran
100 ``lsmod``, or ``ps``. In order to build kdb into the kernel you follow the
101 same steps as you would for kgdb.
105 In theory you would have already also selected an I/O driver such as the
106 ``CONFIG_KGDB_SERIAL_CONSOLE`` interface if you plan on using kdb on a
107 serial port, when you were configuring kgdb.
109 If you want to use a PS/2-style keyboard with kdb, you would select
137 to communicate from gdb to kgdb as well as the devices you want to use
141 is intended to cover the circumstance where you want to use a serial
146 ``kgdbwait`` and early debugging if you build kgdboc into the kernel as
149 Optionally you can elect to activate kms (Kernel Mode Setting)
150 integration. When you use kms with kgdboc and you have a video driver
164 The order listed above must be observed if you use any of the optional
174 depending on if you are using kdb and/or kgdb, in one of the following
175 scenarios. The order listed above must be observed if you use any of the
194 Here are two examples of how you might format the kgdboc string. The
205 At run time you can enable or disable kgdboc by echoing a parameters
218 You do not need to specify the baud if you are configuring the
225 depending on if you are using kdb and/or kgdb, in one of the following
259 protocol. You must manually send a :kbd:`SysRq-G` unless you have a proxy
263 for you.
265 When using kgdboc with no debugger proxy, you can end up connecting the
266 debugger at one of two entry points. If an exception occurs after you
268 waiting for the debugger. In this case you disconnect your terminal
269 program and then connect the debugger in its place. If you want to
270 interrupt the target system and forcibly enter a debug session you have
271 to issue a :kbd:`Sysrq` sequence and then type the letter :kbd:`g`. Then you
272 disconnect the terminal session and connect gdb. Your options if you
273 don't like this are to hack gdb to send the :kbd:`SysRq-G` for you as well as
280 If you specify the kernel parameter ``kgdboc_earlycon`` and your serial
288 sufficient to make this work. If you have more than one boot console you
293 For instance, on one board to be explicit you might do::
297 If the only boot console on the device was "qcom_geni", you could simplify::
306 option if you compiled a kgdb I/O driver into the kernel and you
313 architecture allows when you use this option. If you build the kgdb I/O
319 The ``kgdbcon`` feature allows you to see printk() messages inside gdb
337 If you do this after you configure the kgdb I/O driver, the
354 The kgdbreboot feature allows you to change how the debugger deals with
378 If the architecture that you are using enable KASLR by default,
379 you should consider turning it off. KASLR randomizes the
398 Configure kgdboc after the kernel has booted; assuming you are using
404 fault. There are several ways you can enter the kernel debugger
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::
416 - When you have telneted to a terminal server that supports sending
425 3. From the kdb prompt you can run the ``help`` command to see a complete
440 4. When you are done using kdb you need to consider rebooting the system
441 or using the ``go`` command to resuming normal kernel execution. If you
444 time could be adversely affected, so you should take this into
463 fault. There are several ways you can enter the kernel debugger
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::
501 In order to use kgdb you must activate it by passing configuration
502 information to one of the kgdb I/O drivers. If you do not pass any
505 loaded and configured. If you unconfigure a kgdb I/O driver, kgdb will
539 - When logged in as root or with a super user session you can run::
547 - When you have telneted to a terminal server that supports sending
571 Once connected, you can debug a kernel the way you would debug an
574 If you are having problems connecting or something is going seriously
575 wrong while debugging, it will most often be the case that you want
581 Remember if you continue in gdb, and need to "break in" again, you need
583 putting a breakpoint at ``sys_sync`` and then you can run ``sync`` from a
590 core will remember which you used the last time and automatically start
599 There are two ways to switch from kgdb to kdb: you can use gdb to issue
600 a maintenance packet, or you can blindly type the command ``$3#33``.
602 message ``KGDB or $3#33 for KDB``. It is important to note that you have
616 Now you must kill gdb. Typically you press :kbd:`CTRL-Z` and issue
624 There are two ways you can change from kdb to kgdb. You can manually
626 or you can connect gdb while the kdb shell prompt is active. The kdb
647 operations if you have gdb connected. The more useful commands to run
649 information commands. To see all the kdb commands you can run
668 When kgdb is enabled in the kernel config you can also elect to enable
766 you can build the kdb_hello.ko kernel module from
767 ``samples/kdb/kdb_hello.c``. To build this example you can set
769 config. Later run ``modprobe kdb_hello`` and the next time you
770 enter the kdb shell, you can run the ``hello`` command.
801 If you are intent on adding kgdb architecture specific support for a new
804 architecture, and at that point you must create an architecture specific
864 debugger detaches. You need to be very careful with any kind of lock you
885 switch to a text context when you are using ``kgdboc=kms,kbd``, provided
886 that you have a video driver which has a frame buffer console and atomic