| /linux-3.4.99/arch/cris/ |
| D | Kconfig.debug | 15 The CRIS version of gdb can be used to remotely debug a running
16 Linux kernel via the serial debug port. Provided you have gdb-cris
17 installed, run gdb-cris vmlinux, then type
19 (gdb) set remotebaud 115200 <- kgdb uses 115200 as default
20 (gdb) target remote /dev/ttyS0 <- maybe you use another port
23 didn't before). The kernel halts when it boots, waiting for gdb if
38 delivering a terminating SIGSEGV to allow debugging with gdb.
|
| /linux-3.4.99/arch/mn10300/kernel/ |
| D | Makefile | 20 obj-$(CONFIG_GDBSTUB) += gdb-stub.o gdb-low.o
21 obj-$(CONFIG_GDBSTUB_ON_TTYSx) += gdb-io-serial.o gdb-io-serial-low.o
22 obj-$(CONFIG_GDBSTUB_ON_TTYSMx) += gdb-io-ttysm.o gdb-io-ttysm-low.o
|
| /linux-3.4.99/fs/ext3/ |
| D | resize.c | 228 struct buffer_head *gdb; in setup_new_group_blocks() local
236 gdb = sb_getblk(sb, block); in setup_new_group_blocks()
237 if (!gdb) { in setup_new_group_blocks()
241 if ((err = ext3_journal_get_write_access(handle, gdb))) { in setup_new_group_blocks()
242 brelse(gdb); in setup_new_group_blocks()
245 lock_buffer(gdb); in setup_new_group_blocks()
246 memcpy(gdb->b_data, sbi->s_group_desc[i]->b_data, gdb->b_size); in setup_new_group_blocks()
247 set_buffer_uptodate(gdb); in setup_new_group_blocks()
248 unlock_buffer(gdb); in setup_new_group_blocks()
249 err = ext3_journal_dirty_metadata(handle, gdb); in setup_new_group_blocks()
[all …]
|
| /linux-3.4.99/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 89 11.1 Starting the kernel under gdb
93 11.5 Attaching gdb to the kernel
2473 possible to debug it with gdb almost like any other process. It is
2475 ptraced for system call interception, so gdb can't ptrace them.
2483 ptrace proxy so that gdb works with UML, respectively.
2488 11.1. Starting the kernel under gdb
2490 You can have the kernel running under the control of gdb from the
2492 xterm with gdb running inside it. The kernel will send some commands
2493 to gdb which will leave it stopped at the beginning of start_kernel.
2506 you ^C gdb and get a backtrace, you will see the idle thread, which
[all …]
|
| /linux-3.4.99/arch/h8300/ |
| D | Kconfig.debug | 32 bool "Use gdb stub"
35 gdb stub exception support
38 bool "Use gdb protocol serial console"
|
| D | README | 28 gdb-5.2 or higher
|
| /linux-3.4.99/Documentation/ |
| D | BUG-HUNTING | 203 gdb vmlinux
204 (gdb) l *0xc021e50e
214 gdb vmlinux
215 (gdb) p vt_ioctl
216 (gdb) l *(0x<address of vt_ioctl> + 0xda8)
218 (gdb) l *(vt_ioctl + 0xda8)
226 this shows the problem in the :jbd: module. You can load that module in gdb
228 gdb fs/jbd/jbd.ko
229 (gdb) p log_wait_commit
230 (gdb) l *(0x<address> + 0xa3)
[all …]
|
| D | debugging-via-ohci1394.txt | 72 There is also a gdb proxy for firewire which allows to use gdb to access
73 data which can be referenced from symbols found by gdb in vmlinux:
76 The latest version of this gdb proxy (fireproxy-0.34) can communicate (not
|
| D | oops-tracing.txt | 66 gdb /usr/src/linux/vmlinux
67 gdb> disassemble <offending_function>
108 and then you get a better idea of what happens than with the gdb
|
| /linux-3.4.99/arch/frv/kernel/ |
| D | Makefile | 15 obj-$(CONFIG_GDBSTUB) += gdb-stub.o gdb-io.o
|
| /linux-3.4.99/Documentation/frv/ |
| D | gdbstub.txt | 78 frv-uclinux-gdb linux [uClinux]
82 frv-uclinux-gdb vmlinux [MMU linux]
86 GNU gdb frv-031024
93 (gdb)
97 (gdb) target remote /dev/ttyS0
100 (gdb)
|
| D | mmu-layout.txt | 209 The gdb-stub included in this kernel provides a number of services to aid in the debugging of MMU
213 variable is defined in arch/frv/kernel/gdb-stub.c. Note that the gdbinit file in this
220 (gdb) _tlb
239 (gdb) _amr
259 (gdb) _pgd
290 (gdb) _ptd_d
|
| /linux-3.4.99/Documentation/zh_CN/ |
| D | oops-tracing.txt | 57 使用在Documentation/kdump/gdbmacros.txt中定义的dmesg gdb宏，从旧的内存中提取内核
74 gdb /usr/src/linux/vmlinux
75 gdb> disassemble <offending_function>
106 然后你会比gdb反汇编更清楚的知道发生了什么。
|
| /linux-3.4.99/fs/ext4/ |
| D | resize.c | 464 struct buffer_head *gdb; in setup_new_flex_group_blocks() local
471 gdb = sb_getblk(sb, block); in setup_new_flex_group_blocks()
472 if (!gdb) { in setup_new_flex_group_blocks()
477 err = ext4_journal_get_write_access(handle, gdb); in setup_new_flex_group_blocks()
479 brelse(gdb); in setup_new_flex_group_blocks()
482 memcpy(gdb->b_data, sbi->s_group_desc[j]->b_data, in setup_new_flex_group_blocks()
483 gdb->b_size); in setup_new_flex_group_blocks()
484 set_buffer_uptodate(gdb); in setup_new_flex_group_blocks()
486 err = ext4_handle_dirty_metadata(handle, NULL, gdb); in setup_new_flex_group_blocks()
488 brelse(gdb); in setup_new_flex_group_blocks()
[all …]
|
| /linux-3.4.99/Documentation/security/ |
| D | Yama.txt | 33 parent to a child process (i.e. direct "gdb EXE" and "strace EXE" still
34 work), or with CAP_SYS_PTRACE (i.e. "gdb --pid=PID", and "strace -p PID"
|
| /linux-3.4.99/Documentation/s390/ |
| D | Debugging390.txt | 38 Stack chaining in gdb by hand
694 If using gdb & you would like accurate displays of registers &
706 some bugs, please make sure you are using gdb-5.0 or later developed
1897 N.B. if compiling for debugging gdb works better without optimisation
1902 gdb <victim program> <optional corefile>
1910 Note gdb's online help is very good use it.
1970 quit: exits gdb.
2005 As an aside unfortunately gdb's, architecture independent watchpoint code
2041 what gdb does when the victim receives certain signals.
2051 Adds directories to be searched for source if gdb cannot find the source.
[all …]
|
| /linux-3.4.99/arch/frv/ |
| D | Kconfig.debug | 16 using gdb. This enlarges your kernel ELF image disk size by several
|
| /linux-3.4.99/Documentation/cgroups/ |
| D | freezer-subsystem.txt | 44 signals is gdb. In fact any program designed to use ptrace is likely to
49 being frozen. This allows the bash example above and gdb to run as
|
| /linux-3.4.99/Documentation/kdump/ |
| D | gdbmacros.txt | 2 # This file contains a few gdb macros (user defined commands) to extract
7 # directory or current directory) or by invoking gdb command with
|
| /linux-3.4.99/arch/xtensa/ |
| D | Kconfig | 207 can be used in gdb:
209 $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
|
| /linux-3.4.99/lib/ |
| D | Kconfig.kgdb | 11 kernel using gdb. It is recommended but not required, that
|
| /linux-3.4.99/arch/mn10300/ |
| D | Kconfig | 308 Enable access to SIF0 through /dev/ttySM0 or gdb-stub
330 Enable access to SIF1 through /dev/ttySM1 or gdb-stub
361 Enable access to SIF2 through /dev/ttySM2 or gdb-stub
|
| D | Kconfig.debug | 44 using gdb. This enlarges your kernel ELF image disk size by several
|
| /linux-3.4.99/ |
| D | README | 364 - Alternately, you can use gdb on a running kernel. (read-only; i.e. you
369 After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore".
370 You can now use all the usual gdb commands. The command to look up the
374 gdb'ing a non-running kernel currently fails because gdb (wrongly)
|
| /linux-3.4.99/arch/sh/ |
| D | Kconfig.debug | 12 Say Y here if your target has the gdb-sh-stub
|