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
67 or on the stack at different points which allows a debugger such as gdb to
111 used for anything in the gdb interface to kgdb. The ``CONFIG_KDB_KEYBOARD``
136 to communicate from gdb to kgdb as well as the devices you want to use
139 For kgdb/gdb, kgdboc is designed to work with a single serial port. It
175 optional configurations together. Using kms + only gdb is generally not
257    Kgdboc does not support interrupting the target via the gdb remote
271 disconnect the terminal session and connect gdb. Your options if you
272 don't like this are to hack gdb to send the :kbd:`SysRq-G` for you as well as
274 unmodified gdb to do the debugging.
318 The ``kgdbcon`` feature allows you to see printk() messages inside gdb
319 while gdb is connected to the kernel. Kdb does not make use of the kgdbcon
322 Kgdb supports using the gdb serial protocol to send console messages to
380 gdb which resolve kernel symbol address from symbol table
497 Using kgdb / gdb
515 Connecting with gdb to a serial port
532    In order to connect to gdb via kgdboc, the kernel must first be
555 3. Connect from gdb
559            % gdb ./vmlinux
560            (gdb) set serial baud 115200
561            (gdb) target remote /dev/ttyS0
566            % gdb ./vmlinux
567            (gdb) target remote 192.168.2.2:2012
575    to enable gdb to be verbose about its target communications. You do
580 Remember if you continue in gdb, and need to "break in" again, you need
598 There are two ways to switch from kgdb to kdb: you can use gdb to issue
609 2. Change from kgdb to kdb with gdb::
615      Now you must kill gdb. Typically you press :kbd:`CTRL-Z` and issue
625 or you can connect gdb while the kdb shell prompt is active. The kdb
626 shell looks for the typical first commands that gdb would issue with the
627 gdb remote protocol and if it sees one of those commands it
634    Now disconnect your terminal program and connect gdb in its place
636 2. At the kdb prompt, disconnect the terminal program and connect gdb in
639 Running kdb commands from gdb
642 It is possible to run a limited set of kdb commands from gdb, using the
643 gdb monitor command. You don't want to execute any of the run control or
645 debugger. You should be using gdb for breakpoints and run control
646 operations if you have gdb connected. The more useful commands to run
653     (gdb) monitor ps
662     (gdb)
728    -  translation to and from gdb specific packet format to struct pt_regs
743    -  All the logic to implement the gdb serial protocol