Home
last modified time | relevance | path

Searched refs:GDB (Results 1 – 25 of 77) sorted by relevance

1234

/openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/crash/crash/
H A Ddonnot-extract-gdb-during-do-compile.patch25 - @if [ ! -f ${GDB}/README ]; then \
26 + @if [ ! -f ${GDB}/${GDB}.patch ]; then \
28 @echo "${LDFLAGS} -lz -ldl -rdynamic" > ${GDB}/gdb/mergelibs
29 @echo "../../${PROGRAM} ../../${PROGRAM}lib.a" > ${GDB}/gdb/mergeobj
34 - @if [ ! -f ${GDB}.tar.gz ] && [ ! -f /usr/bin/wget ]; then \
35 - echo /usr/bin/wget is required to download ${GDB}.tar.gz; echo; exit 1; fi
36 - @if [ ! -f ${GDB}.tar.gz ] && [ -f /usr/bin/wget ]; then \
38 - wget $$WGET_OPTS http://ftp.gnu.org/gnu/gdb/${GDB}.tar.gz; fi
39 - @tar --exclude-from gdb.files -xzmf ${GDB}.tar.gz
H A D0001-cross_add_configure_option.patch18 @echo "../../${PROGRAM} ../../${PROGRAM}lib.a" > ${GDB}/gdb/mergeobj
20 @if [ ! -f ${GDB}/config.status ]; then \
21 - (cd ${GDB}; ./configure ${GDB_CONF_FLAGS} --with-separate-debug-dir=/usr/lib/debug \
22 + (cd ${GDB}; ./configure --host=${GDB_TARGET} --build=${GDB_HOST} --with-separate-debug-dir=/usr…
H A Dgdb_build_jobs_and_not_write_crash_target.patch26 @if [ ! -f ${GDB}/config.status ]; then \
27 …(cd ${GDB}; ./configure --host=${GDB_TARGET} --build=${GDB_HOST} --with-separate-debug-dir=/usr/li…
/openbmc/qemu/tests/tcg/multiarch/
H A DMakefile.target57 ifneq ($(GDB),)
62 --gdb $(GDB) \
69 --gdb $(GDB) \
76 --gdb $(GDB) \
83 --gdb $(GDB) \
90 --gdb $(GDB) \
97 --gdb $(GDB) \
104 --gdb $(GDB) \
111 --gdb $(GDB) \
118 --gdb $(GDB) \
[all …]
/openbmc/qemu/tests/tcg/multiarch/system/
H A DMakefile.softmmu-target17 ifneq ($(GDB),)
22 --gdb $(GDB) \
31 --gdb $(GDB) \
40 --gdb $(GDB) \
54 --gdb $(GDB) \
/openbmc/linux/Documentation/powerpc/
H A Ddawr-power9.rst34 PPC_PTRACE_GETHWDBGINFO call. This results in GDB falling back to
51 For GDB watchpoints (ie 'watch' command) on POWER9 bare metal , GDB
53 support for the watchpoint, GDB will software emulate the watchpoint
57 host. The watchpoint will fail and GDB will fall back to software
60 If a guest is started on a POWER8 host, GDB will accept the watchpoint
65 trapped in GDB. The watchpoint is remembered, so if the guest is
H A Dptrace.rst5 GDB intends to support the following hardware debug features of BookE
12 For that, we need to extend ptrace so that GDB can query and set these
15 that GDB doesn't need to special-case each of them. We added the
21 Query for GDB to discover the hardware debug features. The main info to
25 adding special cases to GDB based on what it sees in AUXV.
28 GDB: this query will return the number of hardware breakpoints, hardware
86 With this GDB can ask for all kinds of hardware breakpoints and watchpoints
/openbmc/linux/Documentation/translations/zh_CN/rust/
H A Dquick-start.rst205 如果使用的是GDB/Binutils，而Rust符号没有被demangled，原因是工具链还不支持Rust的新v0
208 - 安装一个较新的版本（GDB >= 10.2, Binutils >= 2.36）。
210 - 一些版本的GDB（例如vanilla GDB 10.1）能够使用嵌入在调试信息(``CONFIG_DEBUG_INFO``)
/openbmc/openbmc/poky/meta/recipes-connectivity/openssh/openssh/
H A Drun-ptest26 GDB=`which gdb`
28 if [ -z "${SSHAGENT}" -o -z "${GDB}" ]; then
/openbmc/openbmc/poky/meta/recipes-devtools/tcltk/tcl/
H A Dfix_non_native_build_issue.patch28 - $(GDB) ./${TCLTEST_EXE} --command=gdb.run
29 + $(GDB) ${TCLTEST_EXE} --command=gdb.run
54 - $(SHELL_ENV) $(GDB) ./${TCL_EXE}
55 + $(SHELL_ENV) $(GDB) ${TCL_EXE}
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/cgdb/
H A Dcgdb_0.8.0.bb1 SUMMARY = "curses-based interface to GDB"
2 DESCRIPTION = "cgdb is a lightweight curses (terminal-based) interface to the GNU Debugger (GDB)."
/openbmc/openbmc/poky/meta/recipes-core/packagegroups/
H A Dpackagegroup-cross-canadian.bb11 GDB = "gdb-cross-canadian-${TRANSLATED_TARGET_ARCH}"
16 ${@all_multilib_tune_values(d, 'GDB')} \
/openbmc/qemu/tests/tcg/aarch64/
H A DMakefile.target117 ifneq ($(GDB),)
122 --gdb $(GDB) \
129 --gdb $(GDB) \
139 --gdb $(GDB) \
/openbmc/qemu/tests/tcg/s390x/
H A DMakefile.target91 ifneq ($(GDB),)
96 --gdb $(GDB) \
105 --gdb $(GDB) \
/openbmc/qemu/docs/system/
H A Dgdb.rst3 GDB usage
52 While GDB can always fall back to inserting breakpoints into memory
85 GDB's abstraction for debugging targets with multiple possible
174 an interrupt vector the behavior can be controlled from GDB. There are
210 Another feature that QEMU gdbstub provides is to toggle the memory GDB
211 works with, by default GDB will show the current process memory respecting
232 Connecting to the GDB socket allows running arbitrary code inside the guest;
238 The GDB socket is not protected by authentication, authorization or encryption.
H A Dtarget-avr.rst33 - Debugging with GDB debugger::
41 and then within GDB shell::
H A Dtarget-rx.rst6 Use the executable ``qemu-system-rx`` to simulate RX target (GDB simulator).
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/nana/
H A Dnana_git.bb41 sed -i -e 's:@GDB@:\$\{GDB\}:g' ${S}/src/nana-run.in
/openbmc/qemu/
H A D.gdbinit1 # GDB may have ./.gdbinit loading disabled by default. In that case you can
/openbmc/qemu/tests/tcg/
H A DREADME11 GDB scripts for exercising the gdbstub on specific tests will be found
/openbmc/openbmc/poky/documentation/dev-manual/
H A Ddebugging.rst895 Debugging With the GNU Project Debugger (GDB) Remotely
904 information on GDB at https://sourceware.org/gdb/.
976 the host GDB. The host GDB then sends control commands to gdbserver to
983 Because the host GDB is responsible for loading the debugging
996 "inferior" binary. For documentation on GDB see the `GDB
1038 Build the cross GDB component and
1076 #. *Set up GDB:*
1104 additional gdbserver options, see the `GDB Server
1147 Debugging with the GNU Project Debugger (GDB) on the Target
1150 The previous section addressed using GDB remotely for debugging
[all …]
/openbmc/linux/Documentation/bpf/
H A Ds390.rst173 It is possible to debug the s390 kernel using QEMU GDB stub, which is activated
181 GDB can then be attached using the following command::
205 - `Using GDB with QEMU <https://wiki.osdev.org/Kernel_Debugging#Use_GDB_with_QEMU>`_
/openbmc/docs/
H A Dcheatsheet.md195 ## GDB section in OpenBMC cheatsheet
197 [SDK build](#building-the-openbmc-sdk) provides GDB and debug symbols:
199 - `$GDB` is available to use once SDK environment is setup
202 To use GDB:
205 2. Run below GDB commands:
208 $GDB <relative_path_to_exeutable> <path_to_core_file>
/openbmc/linux/Documentation/rust/
H A Dquick-start.rst247 If GDB/Binutils is used and Rust symbols are not getting demangled, the reason
251 - Install a newer release (GDB >= 10.2, Binutils >= 2.36).
253 - Some versions of GDB (e.g. vanilla GDB 10.1) are able to use
/openbmc/u-boot/doc/
H A DREADME.qemu-mips152 GDB is free software, covered by the GNU General Public License, and you are
155 There is absolutely no warranty for GDB. Type "show warranty" for details.
156 This GDB was configured as "--host=i486-linux-gnu --target=mipsel-unknown-linux-gnu"...

1234