Lines Matching refs:gdb
26 kernel. It is used along with gdb to debug a Linux kernel. The
27 expectation is that gdb can be used to "break in" to the kernel to
29 similar to the way an application developer would use gdb to debug an
36 instance of gdb against the vmlinux file which contains the symbols (not
37 a boot image such as bzImage, zImage, uImage...). In gdb the developer
39 connection a developer makes with gdb depends on the availability of
59 file, gdb tends not to be very useful without the symbolic data, so you
68 such as gdb to more accurately construct stack back traces while
112 used for anything in the gdb interface to kgdb. The ``CONFIG_KDB_KEYBOARD``
137 to communicate from gdb to kgdb as well as the devices you want to use
140 For kgdb/gdb, kgdboc is designed to work with a single serial port. It
176 optional configurations together. Using kms + only gdb is generally not
258 Kgdboc does not support interrupting the target via the gdb remote
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
275 unmodified gdb to do the debugging.
295 The ``kgdbcon`` feature allows you to see :c:func:`printk` messages inside gdb
296 while gdb is connected to the kernel. Kdb does not make use of the kgdbcon
299 Kgdb supports using the gdb serial protocol to send console messages to
357 gdb which resolve kernel symbol address from symbol table
474 Using kgdb / gdb
492 Connecting with gdb to a serial port
509 In order to connect to gdb via kgdboc, the kernel must first be
532 3. Connect from gdb
536 % gdb ./vmlinux
537 (gdb) set remotebaud 115200
538 (gdb) target remote /dev/ttyS0
543 % gdb ./vmlinux
544 (gdb) target remote 192.168.2.2:2012
552 to enable gdb to be verbose about its target communications. You do
557 Remember if you continue in gdb, and need to "break in" again, you need
575 There are two ways to switch from kgdb to kdb: you can use gdb to issue
586 2. Change from kgdb to kdb with gdb::
592 Now you must kill gdb. Typically you press :kbd:`CTRL-Z` and issue
602 or you can connect gdb while the kdb shell prompt is active. The kdb
603 shell looks for the typical first commands that gdb would issue with the
604 gdb remote protocol and if it sees one of those commands it
611 Now disconnect your terminal program and connect gdb in its place
613 2. At the kdb prompt, disconnect the terminal program and connect gdb in
616 Running kdb commands from gdb
619 It is possible to run a limited set of kdb commands from gdb, using the
620 gdb monitor command. You don't want to execute any of the run control or
622 debugger. You should be using gdb for breakpoints and run control
623 operations if you have gdb connected. The more useful commands to run
630 (gdb) monitor ps
639 (gdb)
705 - translation to and from gdb specific packet format to :c:type:`pt_regs`
720 - All the logic to implement the gdb serial protocol