Home
last modified time | relevance | path

Searched refs:gdb (Results 1 – 41 of 41) sorted by relevance

/linux-4.1.27/scripts/gdb/linux/
Dsymbols.py14 import gdb
22 if hasattr(gdb, 'Breakpoint'):
23 class LoadModuleBreakpoint(gdb.Breakpoint):
30 module = gdb.parse_and_eval("mod")
40 show_pagination = gdb.execute("show pagination", to_string=True)
42 gdb.execute("set pagination off")
45 gdb.write("refreshing all symbols to reload module "
52 gdb.execute("set pagination %s" % ("on" if pagination else "off"))
57 class LxSymbols(gdb.Command):
72 super(LxSymbols, self).__init__("lx-symbols", gdb.COMMAND_FILES,
[all …]
Dcpus.py14 import gdb
24 return gdb.selected_thread().num - 1
26 tid = gdb.selected_thread().ptid[2]
32 raise gdb.GdbError("Sorry, obtaining the current CPU is not yet "
40 offset = gdb.parse_and_eval(
44 offset = gdb.parse_and_eval(
46 except gdb.error:
59 gdb.events.stop.disconnect(cpu_mask_invalidate)
60 if hasattr(gdb.events, 'new_objfile'):
61 gdb.events.new_objfile.disconnect(cpu_mask_invalidate)
[all …]
Dutils.py14 import gdb
24 gdb.events.new_objfile.disconnect(self._new_objfile_handler)
28 self._type = gdb.lookup_type(self._name)
30 raise gdb.GdbError(
32 if hasattr(gdb, 'events') and hasattr(gdb.events, 'new_objfile'):
33 gdb.events.new_objfile.connect(self._new_objfile_handler)
46 element = gdb.Value(0).cast(typeobj)
55 class ContainerOf(gdb.Function):
66 return container_of(ptr, gdb.lookup_type(typename.string()).pointer(),
80 endian = gdb.execute("show endian", to_string=True)
[all …]
Ddmesg.py14 import gdb
20 class LxDmesg(gdb.Command):
24 super(LxDmesg, self).__init__("lx-dmesg", gdb.COMMAND_DATA)
27 log_buf_addr = int(str(gdb.parse_and_eval("log_buf")).split()[0], 16)
28 log_first_idx = int(gdb.parse_and_eval("log_first_idx"))
29 log_next_idx = int(gdb.parse_and_eval("log_next_idx"))
30 log_buf_len = int(gdb.parse_and_eval("log_buf_len"))
32 inf = gdb.inferiors()[0]
48 gdb.write("Corrupted log buffer!\n")
58 gdb.write("[{time:12.6f}] {line}\n".format(
Dmodules.py14 import gdb
25 modules = gdb.parse_and_eval("modules")
41 class LxModule(gdb.Function):
56 raise gdb.GdbError("Unable to find MODULE " + mod_name)
62 class LxLsmod(gdb.Command):
68 super(LxLsmod, self).__init__("lx-lsmod", gdb.COMMAND_DATA)
71 gdb.write(
76 gdb.write("{address} {name:<19} {size:>8} {ref}".format(
88 gdb.write("{separator}{name}".format(
93 gdb.write("\n")
Dtasks.py14 import gdb
24 init_task = gdb.parse_and_eval("init_task").address
48 class LxTaskByPidFunc(gdb.Function):
62 raise gdb.GdbError("No task of PID " + str(pid))
79 ia64_task_size = gdb.parse_and_eval("sizeof(struct task_struct)")
87 class LxThreadInfoFunc (gdb.Function):
DMakefile1 always := gdb-scripts
5 $(obj)/gdb-scripts:
/linux-4.1.27/Documentation/
Dgdb-kernel-debugging.txt1 Debugging kernel and modules via gdb
6 using gdb. Gdb comes with a powerful scripting interface for python. The
10 be transferred to the other gdb stubs as well.
16 o gdb 7.2+ (recommended: 7.4+) with python support enabled (typically true
39 o Enable the gdb stub of QEMU/KVM, either
47 o Start gdb: gdb vmlinux
49 Note: Some distros may restrict auto-loading of gdb scripts to known safe
50 directories. In case gdb reports to refuse loading vmlinux-gdb.py, add
54 to ~/.gdbinit. See gdb help for more details.
57 (gdb) target remote :1234
[all …]
DBUG-HUNTING203 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 …]
Ddebugging-via-ohci1394.txt70 There is also a gdb proxy for firewire which allows to use gdb to access
71 data which can be referenced from symbols found by gdb in vmlinux:
74 The latest version of this gdb proxy (fireproxy-0.34) can communicate (not
Doops-tracing.txt66 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
Dkmemcheck.txt545 not been initialized. We can verify this using gdb:
547 $ gdb vmlinux
549 (gdb) p &((struct siginfo *) 0)->_sifields
Dkernel-parameters.txt1653 gdb or control-c on the dbgp connection. When
/linux-4.1.27/arch/cris/
DKconfig.debug15 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-4.1.27/arch/mn10300/kernel/
DMakefile20 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-4.1.27/scripts/gdb/
Dvmlinux-gdb.py19 gdb.parse_and_eval("0")
20 gdb.execute("", to_string=True)
22 gdb.write("NOTE: gdb 7.2 or later required for Linux helper scripts to "
/linux-4.1.27/fs/ext3/
Dresize.c228 struct buffer_head *gdb; in setup_new_group_blocks() local
236 gdb = sb_getblk(sb, block); in setup_new_group_blocks()
237 if (unlikely(!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-4.1.27/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt89 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-4.1.27/arch/frv/kernel/
DMakefile15 obj-$(CONFIG_GDBSTUB) += gdb-stub.o gdb-io.o
/linux-4.1.27/Documentation/frv/
Dgdbstub.txt78 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)
Dmmu-layout.txt209 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-4.1.27/Documentation/zh_CN/
Doops-tracing.txt57 使用在Documentation/kdump/gdbmacros.txt中定义的dmesg gdb宏，从旧的内存中提取内核
74 gdb /usr/src/linux/vmlinux
75 gdb> disassemble <offending_function>
106 然后你会比gdb反汇编更清楚的知道发生了什么。
/linux-4.1.27/scripts/
DMakefile39 subdir-$(CONFIG_GDB_SCRIPTS) += gdb
/linux-4.1.27/fs/ext4/
Dresize.c522 struct buffer_head *gdb; in setup_new_flex_group_blocks() local
529 gdb = sb_getblk(sb, block); in setup_new_flex_group_blocks()
530 if (unlikely(!gdb)) { in setup_new_flex_group_blocks()
535 BUFFER_TRACE(gdb, "get_write_access"); in setup_new_flex_group_blocks()
536 err = ext4_journal_get_write_access(handle, gdb); in setup_new_flex_group_blocks()
538 brelse(gdb); in setup_new_flex_group_blocks()
541 memcpy(gdb->b_data, sbi->s_group_desc[j]->b_data, in setup_new_flex_group_blocks()
542 gdb->b_size); in setup_new_flex_group_blocks()
543 set_buffer_uptodate(gdb); in setup_new_flex_group_blocks()
545 err = ext4_handle_dirty_metadata(handle, NULL, gdb); in setup_new_flex_group_blocks()
[all …]
/linux-4.1.27/Documentation/s390/
DDebugging390.txt33 Stack chaining in gdb by hand
727 If using gdb & you would like accurate displays of registers &
739 some bugs, please make sure you are using gdb-5.0 or later developed
1572 N.B. if compiling for debugging gdb works better without optimisation
1577 gdb <victim program> <optional corefile>
1585 Note gdb's online help is very good use it.
1646 quit: exits gdb.
1681 As an aside unfortunately gdb's, architecture independent watchpoint code
1717 what gdb does when the victim receives certain signals.
1727 Adds directories to be searched for source if gdb cannot find the source.
[all …]
/linux-4.1.27/
D.gitignore47 /vmlinux-gdb.py
DREADME392 - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
397 After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore".
398 You can now use all the usual gdb commands. The command to look up the
402 gdb'ing a non-running kernel currently fails because gdb (wrongly)
DMakefile932 $(Q)ln -fsn `cd $(srctree) && /bin/pwd`/scripts/gdb/vmlinux-gdb.py
1182 signing_key.x509.signer vmlinux-gdb.py
DMAINTAINERS4305 F: scripts/gdb/
/linux-4.1.27/Documentation/security/
DYama.txt33 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-4.1.27/arch/frv/
DKconfig.debug12 using gdb. This enlarges your kernel ELF image disk size by several
/linux-4.1.27/Documentation/kdump/
Dgdbmacros.txt2 # This file contains a few gdb macros (user defined commands) to extract
7 # directory or current directory) or by invoking gdb command with
Dkdump.txt459 gdb vmlinux <dump-file>
/linux-4.1.27/Documentation/cgroups/
Dfreezer-subsystem.txt44 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-4.1.27/arch/mn10300/
DKconfig305 Enable access to SIF0 through /dev/ttySM0 or gdb-stub
327 Enable access to SIF1 through /dev/ttySM1 or gdb-stub
358 Enable access to SIF2 through /dev/ttySM2 or gdb-stub
DKconfig.debug40 using gdb. This enlarges your kernel ELF image disk size by several
/linux-4.1.27/fs/proc/
DKconfig36 be read with gdb and other ELF tools. No modifications can be
/linux-4.1.27/arch/sh/
DKconfig.debug12 Say Y here if your target has the gdb-sh-stub
/linux-4.1.27/arch/xtensa/
DKconfig200 use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
201 xt-gdb can't place a Software Breakpoint in the 0XD region prior
203 was mapped gdb wouldn't remove the breakpoint on hitting it as the
/linux-4.1.27/lib/
DKconfig.kgdb11 kernel using gdb. It is recommended but not required, that
DKconfig.debug128 tools like crash, kgdb, LKCD, gdb, etc on the kernel.
156 Requires recent gcc (4.7+) and recent gdb/binutils.
166 of gcc and gdb. It makes the debug information larger.
168 variables in gdb on optimized code.
175 build directory. If you load vmlinux into gdb, the helper
176 scripts will be automatically imported by gdb as well, and
178 instance. See Documentation/gdb-kernel-debugging.txt for further
1655 firescope and access all memory below 4GB using fireproxy from gdb.