Searched refs:gdb (Results 76 – 85 of 85) sorted by relevance
1234
| /qemu/docs/system/ |
| H A D | target-avr.rst | 39 avr-gdb demo.elf
|
| /qemu/docs/about/ |
| H A D | emulation.rst | 135 Semihosting calls can be re-directed to a (potentially remote) gdb
159 is performed on input or output. This is because gdb semihosting
|
| /qemu/qapi/ |
| H A D | dump.json | 55 # allows using gdb to process the core file.
|
| /qemu/docs/user/ |
| H A D | main.rst | 91 Wait gdb connection to port
|
| /qemu/docs/devel/ |
| H A D | testing.rst | 58 ``gdb``. However there can still be differences in behavior between ``make``
245 * ``-gdb`` wraps every QEMU invocation in a ``gdbserver``, which waits for a
246 connection from a gdb client. The options given to ``gdbserver`` (e.g. the
251 ``gdb -iex "target remote $addr"``, where ``$addr`` is the address
253 If the ``-gdb`` option is not used, ``$GDB_OPTIONS`` is ignored,
|
| H A D | loads-stores.rst | 397 like writes from the gdb debug stub or initial loading of ROM contents.
|
| /qemu/ |
| H A D | qemu-options.hx | 4445 DEF("gdb", HAS_ARG, QEMU_OPTION_gdb, \
4446 "-gdb dev accept gdb connection on 'dev'. (QEMU defaults to starting\n"
4451 ``-gdb dev``
4455 connect with gdb and issue a ``continue`` command, you will need to
4460 -gdb tcp::3117
4464 allows you to start QEMU from within gdb and establish the
4469 (gdb) target remote | exec |qemu_system| -gdb stdio ...
4477 Shorthand for -gdb tcp::1234, i.e. open a gdbserver on TCP port 1234
4885 ``target=native|gdb|auto``
4888 means ``gdb`` during debug sessions and ``native`` otherwise.
[all …]
|
| H A D | MAINTAINERS | 105 F: gdb-xml/s390*.xml
222 F: gdb-xml/avr-cpu.xml
246 F: gdb-xml/hexagon*.xml
469 F: gdb-xml/s390*.xml
1254 F: gdb-xml/loongarch*.xml
3019 F: docs/system/gdb.rst
3023 F: gdb-xml/
3026 F: scripts/probe-gdb-support.py
|
| H A D | configure | 758 --gdb=*) gdb_bin="$optarg"
|
| H A D | hmp-commands.hx | 1096 gdb. Without ``-z|-l|-s|-w``, the dump format is ELF.
|
1234