Lines Matching refs:GDB
23 This file documents the GNU debugger GDB.
25 This is the Tenth Edition, of `Debugging with GDB: the GNU
26 Source-Level Debugger' for GDB (GDB) Version 7.3.1.
44 File: gdb.info, Node: GDB/MI Program Execution, Next: GDB/MI Stack Manipulation, Prev: GDB/MI Th…
46 27.11 GDB/MI Program Execution
50 record `*stopped'. Currently GDB only really executes asynchronously
79 GDB Command
82 The corresponding GDB corresponding is `continue'.
109 GDB Command
112 The corresponding GDB command is `finish'.
127 Function returning other than `void'. The name of the internal GDB
163 GDB Command
166 The corresponding GDB command is `interrupt'.
201 GDB Command
204 The corresponding GDB command is `jump'.
230 GDB Command
233 The corresponding GDB command is `next'.
263 GDB Command
266 The corresponding GDB command is `nexti'.
291 GDB Command
294 The corresponding GDB command is `return'.
341 GDB Command
344 The corresponding GDB command is `run'.
382 such as `SIGINT'. In this case, GDB/MI displays this:
403 GDB Command
406 The corresponding GDB command is `step'.
441 output, once GDB has stopped, will vary depending on whether we have
445 GDB Command
448 The corresponding GDB command is `stepi'.
484 GDB Command
487 The corresponding GDB command is `until'.
502 File: gdb.info, Node: GDB/MI Stack Manipulation, Next: GDB/MI Variable Objects, Prev: GDB/MI Pro…
504 27.12 GDB/MI Stack Manipulation Commands
517 GDB Command
520 The corresponding GDB command is `info frame' or `frame' (without
544 GDB Command
547 There's no equivalent GDB command.
597 GDB Command
600 GDB does not have an equivalent command. `gdbtk' has a `gdb_get_args'
702 GDB Command
705 The corresponding GDB commands are `backtrace' and `where'.
783 GDB Command
786 `info locals' in GDB, `gdb_get_locals' in `gdbtk'.
840 GDB Command
843 The corresponding GDB commands are `frame', `up', `down',
855 File: gdb.info, Node: GDB/MI Variable Objects, Next: GDB/MI Data Manipulation, Prev: GDB/MI Stac…
857 27.13 GDB/MI Variable Objects
932 variable object is updated, GDB makes sure that the thread/frame
936 The following is the complete set of GDB/MI operations defined to
972 GDB allows Python-based visualizers to affect the output of the MI
979 Note that if Python support has not been compiled into GDB, this
982 This feature is currently (as of GDB 7.0) experimental, and may work
983 differently in future versions of GDB.
1021 cases. If the `-enable-pretty-printing' command is not sent, then GDB
1046 would be printed by the GDB CLI.
1239 returned as a string in the same format as it is output by the GDB CLI:
1403 either through recompilation or by using the GDB `file'
1408 should be prepared for this possibility. *Note GDB/MI Development
1409 and Front Ends: GDB/MI Development and Front Ends.
1426 that GDB knows about, but because dynamic varobjs lazily
1431 number of children known by GDB. This is the only way to detect
1528 argument. GDB will call this object with the value of the varobj NAME
1540 command `-list-features' (*note GDB/MI Miscellaneous Commands::) can be
1566 File: gdb.info, Node: GDB/MI Data Manipulation, Next: GDB/MI Tracepoint Commands, Prev: GDB/MI V…
1568 27.14 GDB/MI Data Manipulation
1571 This section describes the GDB/MI commands that manipulate data:
1627 manipulated directly by GDB/MI, i.e., it is not possible to adjust its
1630 GDB Command
1715 GDB Command
1718 The corresponding GDB commands are `print', `output', and `call'. In
1725 "tokens" described in *Note GDB/MI Command Syntax: GDB/MI Command
1726 Syntax. Notice how GDB/MI returns the same tokens in its output.
1751 GDB Command
1754 GDB doesn't have a direct analog for this command; `gdbtk' has the
1792 GDB Command
1795 GDB does not have a command which corresponds to
1851 GDB Command
1854 The corresponding GDB commands are `info reg', `info all-reg', and (in
1928 the same as for GDB's `print' command (*note Output Formats:
1961 GDB Command
1964 The corresponding GDB command is `x'. `gdbtk' has `gdb_get_mem' memory
2043 Attributes::. Second, GDB will attempt to read the remaining regions.
2044 For each one, if reading full region results in an errors, GDB will try
2049 address, which is not practical. Therefore, GDB will attempt to read
2053 range that is neither at the beginning or the end, GDB will not read it.
2055 The result record (*note GDB/MI Result Records::) that is output of
2074 GDB Command
2077 The corresponding GDB command is `x'.
2108 GDB Command
2111 There's no corresponding GDB command.
2122 File: gdb.info, Node: GDB/MI Tracepoint Commands, Next: GDB/MI Symbol Query, Prev: GDB/MI Data M…
2124 27.15 GDB/MI Tracepoint Commands
2193 *Note GDB/MI Frame Information::, for description of this field.
2196 GDB Command
2199 The corresponding GDB command is `tfind'.
2213 GDB Command
2216 The corresponding GDB command is `tvariable'.
2243 GDB Command
2246 The corresponding GDB command is `tvariables'.
2273 GDB Command
2276 The corresponding GDB command is `tsave'.
2289 GDB Command
2292 The corresponding GDB command is `tstart'.
2323 tracing was automatically stopped when GDB has disconnected. The
2353 tracing will continue after GDB disconnects, `0' means that the
2357 GDB Command
2360 The corresponding GDB command is `tstatus'.
2374 GDB Command
2377 The corresponding GDB command is `tstop'.
2380 File: gdb.info, Node: GDB/MI Symbol Query, Next: GDB/MI File Commands, Prev: GDB/MI Tracepoint C…
2382 27.16 GDB/MI Symbol Query Commands
2397 GDB Command
2400 There is no corresponding GDB command.
2411 File: gdb.info, Node: GDB/MI File Commands, Next: GDB/MI Target Manipulation, Prev: GDB/MI Symbo…
2413 27.17 GDB/MI File Commands
2416 This section describes the GDB/MI commands to specify executable file
2430 are set when using this command with no arguments, GDB will produce
2434 GDB Command
2437 The corresponding GDB command is `file'.
2457 file. If used without argument, GDB clears the information about the
2461 GDB Command
2464 The corresponding GDB command is `exec-file'.
2487 GDB Command
2490 The GDB equivalent is `info source'
2510 It will always output the filename, but only when GDB can find the
2513 GDB Command
2516 The GDB equivalent is `info sources'. `gdbtk' has an analogous command
2539 without arguments, clears GDB's symbol table info. No output is
2542 GDB Command
2545 The corresponding GDB command is `symbol-file'.
2556 File: gdb.info, Node: GDB/MI Target Manipulation, Next: GDB/MI File Transfer Commands, Prev: GDB…
2558 27.18 GDB/MI Target Manipulation Commands
2569 Attach to a process PID or a file FILE outside of GDB, or a thread
2573 GDB Command
2576 The corresponding GDB command is `attach'.
2600 GDB Command
2603 The corresponding GDB command is `detach'.
2624 GDB Command
2627 The corresponding GDB command is `disconnect'.
2664 Each message is sent as status record (*note GDB/MI Output Syntax:
2665 GDB/MI Output Syntax.).
2681 GDB Command
2684 The corresponding GDB command is `load'.
2740 GDB Command
2758 Connect GDB to the remote target. This command takes two args:
2773 GDB Command
2776 The corresponding GDB command is `target'.
2787 …e: gdb.info, Node: GDB/MI File Transfer Commands, Next: GDB/MI Miscellaneous Commands, Prev: GD…
2789 27.19 GDB/MI File Transfer Commands
2800 Copy file HOSTFILE from the host system (the machine running GDB) to
2803 GDB Command
2806 The corresponding GDB command is `remote put'.
2827 GDB Command
2830 The corresponding GDB command is `remote get'.
2850 GDB Command
2853 The corresponding GDB command is `remote delete'.
2864 File: gdb.info, Node: GDB/MI Miscellaneous Commands, Prev: GDB/MI File Transfer Commands, Up: GD…
2866 27.20 Miscellaneous GDB/MI Commands
2877 Exit GDB immediately.
2879 GDB Command
2899 Set an internal GDB variable.
2901 GDB Command
2904 The corresponding GDB command is `set'.
2922 Show the current value of a GDB variable.
2924 GDB Command
2927 The corresponding GDB command is `show'.
2945 Show version information for GDB. Used mostly in testing.
2947 GDB Command
2950 The GDB equivalent is `show version'. GDB by default shows this
2960 ~GDB is free software, covered by the GNU General Public License, and
2964 ~There is absolutely no warranty for GDB. Type "show warranty" for
2966 ~This GDB was configured as
3020 on which target GDB is using at the moment. Whenever a target can
3032 execution, which means that GDB will accept further commands while
3055 the `--available' option, GDB reports thread groups available on the
3060 with each tuple describing a thread (*note GDB/MI Thread
3158 be established with the `-file-exec-and-symbols' command (*note GDB/MI
3180 GDB Command
3183 The corresponding GDB command is `interpreter-exec'.
3206 GDB Command
3209 The corresponding GDB command is `set inferior-tty' /dev/pts/1.
3229 GDB Command
3232 The corresponding GDB command is `show inferior-tty'.
3258 GDB Command
3289 File: gdb.info, Node: Annotations, Next: JIT Interface, Prev: GDB/MI, Up: Top
3291 28 GDB Annotations
3294 This chapter describes annotations in GDB. Annotations were designed
3295 to interface GDB to graphical user interfaces or other similar programs
3296 which want to interact with GDB at a relatively high level.
3298 The annotation mechanism has largely been superseded by GDB/MI
3299 (*note GDB/MI::).
3305 * Prompting:: Annotations marking GDB's need for input.
3327 characters denotes literal output from GDB. Currently there is no need
3328 for GDB to output a newline followed by two `control-z' characters, but
3334 information GDB prints together with its prompt, values of expressions,
3336 annotations, level 1 is for use when GDB is run as a subprocess of GNU
3338 control GDB, and level 2 annotations have been made obsolete (*note
3342 The GDB command `set annotate' sets the level of annotations to
3350 A simple example of starting up GDB with annotations is:
3355 GDB is free software, covered by the GNU General Public License,
3359 There is absolutely no warranty for GDB. Type "show warranty"
3361 This GDB was configured as "i386-pc-linux-gnu"
3371 Here `quit' is input to GDB; the rest is output from GDB. The three
3373 annotations; the rest is output from GDB.
3382 command history, nor will it affect GDB's notion of which command to
3397 28.3 Annotation for GDB Input
3400 When GDB prompts for input, it annotates this fact so it is possible to
3419 When GDB is prompting for a command (the main GDB prompt).
3422 When GDB prompts for a set of commands, like in the `commands'
3427 When GDB wants the user to select between various overloaded
3431 When GDB wants the user to confirm a potentially dangerous
3435 When GDB is asking the user to press return to continue. Note:
3448 This annotation occurs right before GDB responds to an interrupt.
3452 This annotation occurs right before GDB responds to an error.
3454 Quit and error annotations indicate that any annotations which GDB
3459 necessarily mean that GDB is immediately returning all the way to the
3494 When the program starts executing due to a GDB command such as `step'
3531 The syntax of this annotation is just like `signalled', but GDB is
3563 File: gdb.info, Node: JIT Interface, Next: GDB Bugs, Prev: Annotations, Up: Top
3568 This chapter documents GDB's "just-in-time" (JIT) compilation
3575 being loaded from object files, which is where GDB normally finds the
3577 that use JIT compilation, GDB has an interface that allows the program
3578 to register in-memory symbol files with GDB at runtime.
3580 If you are using GDB to debug a program that uses this interface,
3587 interface. The JIT compiler communicates with GDB by writing data into
3589 GDB attaches, it reads a linked list of symbol files from the global
3633 /* GDB puts a breakpoint in this function. */
3651 To register code with GDB, the JIT should follow this protocol:
3667 When GDB is attached and the breakpoint fires, GDB uses the
3670 to allow GDB to attach to a running process and still find the symbol
3691 GDB and the JIT will leak the memory used for the associated symbol
3695 File: gdb.info, Node: GDB Bugs, Next: Command Line Editing, Prev: JIT Interface, Up: Top
3697 30 Reporting Bugs in GDB
3700 Your bug reports play an essential role in making GDB reliable.
3704 is to help the entire community by making the next version of GDB work
3705 better. Bug reports are your contribution to the maintenance of GDB.
3716 File: gdb.info, Node: Bug Criteria, Next: Bug Reporting, Up: GDB Bugs
3725 is a GDB bug. Reliable debuggers never crash.
3727 * If GDB produces an error message for valid input, that is a bug.
3731 * If GDB does not produce an error message for invalid input, that
3737 for improvement of GDB are welcome in any case.
3740 File: gdb.info, Node: Bug Reporting, Prev: Bug Criteria, Up: GDB Bugs
3746 If you obtained GDB from a support organization, we recommend you
3752 In any event, we also recommend that you submit bug reports for GDB.
3753 The preferred method is to submit them directly using GDB's Bugs web
3758 newsgroups.* Most users of GDB do not want to receive bug reports.
3796 * The version of GDB. GDB announces it if you start with no
3800 looking for the bug in the current version of GDB.
3805 * What compiler (and its version) was used to compile GDB--e.g.
3828 Of course, if the bug is that GDB gets a fatal signal, then we
3835 such as, your copy of GDB is out of synch, or you have encountered
3845 Just run your GDB session inside `script' and then include the
3848 Another way to record a GDB session is to run GDB inside Emacs and
3851 * If you wish to suggest changes to the GDB source, send us context
3852 diffs. If you even discuss something in the GDB source, refer to
3890 Sometimes with a program as complicated as GDB it is very hard to
3906 File: gdb.info, Node: Command Line Editing, Next: Using History Interactively, Prev: GDB Bugs, …
4580 # programs include FTP, Bash, and GDB.
5331 The GDB project mourns the loss of the following long-time contributors:
5334 Fred was a long-standing contributor to GDB (1991-2006), and to
5335 Free Software in general. Outside of GDB, he was known in the
5340 Michael was one of the Global Maintainers of the GDB project, with
5343 behind adding Reverse Debugging to GDB.
5349 File: gdb.info, Node: Formatting Documentation, Next: Installing GDB, Prev: In Memoriam, Up: Top
5354 The GDB 4 release includes an already-formatted reference card, ready
5365 The GDB reference card is designed to print in "landscape" mode on
5370 All the documentation for GDB comes as part of the machine-readable
5377 GDB includes an already formatted copy of the on-line Info version
5388 If you have `makeinfo' installed, and are in the top level GDB
5410 `texinfo.tex' is distributed with GDB and is located in the
5426 File: gdb.info, Node: Installing GDB, Next: Maintenance Commands, Prev: Formatting Documentation…
5428 Appendix C Installing GDB
5433 * Requirements:: Requirements for building GDB
5434 * Running Configure:: Invoking the GDB `configure' script
5435 * Separate Objdir:: Compiling GDB in another directory
5441 File: gdb.info, Node: Requirements, Next: Running Configure, Up: Installing GDB
5443 C.1 Requirements for Building GDB
5446 Building GDB requires various tools and packages to be available.
5449 Tools/Packages Necessary for Building GDB
5453 GDB is written in ISO C90. It should be buildable with any
5457 Tools/Packages Optional for Building GDB
5461 GDB can use the Expat XML parsing library. This library may be
5481 GDB will use the `zlib' library, if available, to read compressed
5483 producing binaries with compressed debug sections. If GDB is
5492 GDB's features related to character sets (*note Character Sets::)
5501 GDB's top-level `configure' and `Makefile' will arrange to build
5506 used by GDB. One easy way to set this up is to download GNU
5511 …db.info, Node: Running Configure, Next: Separate Objdir, Prev: Requirements, Up: Installing GDB
5513 C.2 Invoking the GDB `configure' Script
5516 GDB comes with a `configure' script that automates the process of
5517 preparing GDB for installation; you can then use `make' to build the
5520 The GDB distribution includes all the source code you need for GDB
5524 For example, the GDB version 7.3.1 distribution is in the
5528 script for configuring GDB and all its supporting libraries
5531 the source specific to GDB itself
5554 The simplest way to configure and build GDB is to run `configure'
5560 platform on which GDB will run as an argument.
5569 identifies the platform where GDB will run. (You can often leave off
5602 environment variable) is publicly readable. Remember that GDB uses the
5603 shell to start your program--some systems refuse to let GDB debug child
5607 …db.info, Node: Separate Objdir, Next: Config Names, Prev: Running Configure, Up: Installing GDB
5609 C.3 Compiling GDB in Another Directory
5612 If you want to run GDB versions for several host or target machines,
5627 For example, with version 7.3.1, you can build GDB in a separate
5640 directory `gdb-sun4/libiberty', and GDB itself in `gdb-sun4/gdb'.
5645 of GDB, not the whole package. This leads to build errors about
5648 One popular reason to build several GDB configurations in separate
5649 directories is to configure GDB for cross-compiling (where GDB runs on
5662 libraries, and then build GDB.
5670 …db.info, Node: Config Names, Next: Configure Options, Prev: Separate Objdir, Up: Installing GDB
5686 The `configure' script accompanying GDB does not provide any query
5705 `config.sub' is also distributed in the GDB source directory
5709 …Node: Configure Options, Next: System-wide configuration, Prev: Config Names, Up: Installing GDB
5715 most often useful for building GDB. `configure' also has several other
5744 from the GDB source directories. Among other things, you can use
5757 Configure GDB for cross-debugging programs running on the specified
5758 TARGET. Without this option, GDB is configured to debug programs
5759 that run on the same machine (HOST) as GDB itself.
5765 Configure GDB to run on the specified HOST.
5774 File: gdb.info, Node: System-wide configuration, Prev: Configure Options, Up: Installing GDB
5779 GDB can be configured to have a system-wide init file; this file will
5780 be read and executed at startup (*note What GDB does during startup:
5789 If GDB has been configured with the option `--prefix=$prefix', it
5795 if GDB is moved from `$prefix' to `$install', the system init file
5800 it will not be relocated. E.g. if GDB has been configured with
5802 then GDB will always look for `/usr/share/gdb/gdbinit', wherever
5803 GDB is installed.
5806 File: gdb.info, Node: Maintenance Commands, Next: Remote Protocol, Prev: Installing GDB, Up: Top
5811 In addition to commands intended for GDB users, GDB includes a number
5812 of commands intended for GDB developers, that are not documented
5832 breakpoints you've set explicitly, and those GDB is using for
5851 Temporary internal breakpoint used by the GDB `until' command.
5854 Temporary internal breakpoint used by the GDB `finish'
5863 Control whether or not GDB will do "displaced stepping" if the
5871 If the target architecture supports it, GDB will use
5875 GDB will not use displaced stepping to step over breakpoints,
5879 This is the default mode. GDB will use displaced stepping
5898 cause GDB to issue a warning when you use them. The optional
5900 favor of the deprecated one; if it is given, GDB will mention the
5910 Cause GDB to call the internal function `internal_error' or
5914 either quit GDB or create a core file of the current GDB session.
5923 A problem internal to GDB has been detected. Further
5933 When GDB reports an internal problem (error or warning) it gives
5934 the user the opportunity to both quit GDB and create a core file
5935 of the current GDB session. These commands let you override the
5940 You can specify that GDB should always (yes) or never (no)
5944 You can specify that GDB should always (yes) or never (no)
5949 If GDB is talking to an inferior via the serial protocol, then
5951 the response packet. GDB supplies the initial `$' character, the
5960 as a C source file. The created source file can be used in GDB
5964 Prints the contents of GDB's internal dummy-frame stack.
5971 The program being debugged stopped while in a function called from GDB.
5985 Print GDB's internal register data structures.
5998 Print GDB's internal register group data structures. The optional
6014 This command forces GDB to flush its internal register cache.
6058 GDB's data structures, including its flags and contained types.
6066 The default is `off', which means that GDB should try to describe
6068 GDB will instead display the DWARF location expression in an
6070 for GDB to describe simply; in this case you will always see the
6093 disables caching, which will slow down GDB startup, but reduce
6098 Control profiling of GDB.
6103 profiling or exit GDB, the results will be written to a log file.
6104 Remember that if you use profiling, GDB will overwrite the
6109 Configuring with `--enable-profiling' arranges for GDB to be
6116 debug registers values are shown when GDB inserts or removes a
6128 to a nonzero value, GDB will display how much memory each command
6130 requested by invoking GDB with the `--statistics' command-line
6135 set to a nonzero value, GDB will display how much time it took to
6139 by GDB and how much time was spend by the program been debugged.
6141 GDB with the `--statistics' command-line switch (*note Mode
6146 ADDR and an optional section name SECTION. If found, GDB prints
6159 GDB, such as in the test suite.
6162 Set the maximum number of seconds GDB will wait for the target
6163 operation to finish. If this time expires, GDB reports and error
6172 Appendix E GDB Remote Serial Protocol
6204 recognizes a packet meant for GDB.
6209 All GDB commands and responses (other than acknowledgments and
6219 Implementors should note that prior to GDB 5.0 the protocol
6224 That SEQUENCE-ID was appended to the acknowledgment. GDB has never
6225 output SEQUENCE-IDs. Stubs that handle packets added since GDB 5.0
6237 The host (GDB) sends COMMANDs, and the target (the debugging stub
6242 protocol also supports GDB's non-stop execution mode; see *Note Remote
6252 Implementors should note that prior to GDB 5.0, the character `:'
6293 protocol. A newer GDB can tell if a packet is supported based on that
6313 packet's syntax. No GDB packet uses spaces to separate its components.
6316 directly by a BAZ. GDB does not transmit a space character between the
6339 GDB and the stub report support for the `multiprocess' feature using
6428 The first form of the packet is used to detach GDB from the remote
6429 system. It is sent to the remote target before GDB disconnects
6445 A reply from GDB to an `F' packet sent by the target. This is
6457 the `g' packet are determined by the GDB internal gdbarch
6468 each, the following reply indicates to GDB that registers 0
6711 Format::). GDB groups flash memory programming operations
6933 `include/gdb/signals.h' in the GDB source code.
6937 syntax. No GDB stop reply packet uses spaces to separate its
6968 * Otherwise, GDB should ignore this `N:R' pair and go on to the
6981 GDB should use `qXfer:libraries:read' to fetch a new list of
6997 exited process, can be used only when GDB has reported support for
7006 terminated process, can be used only when GDB has reported support
7020 GDB. *Note File-I/O Remote Protocol Extension::, for a list of
7026 The target replies with this packet when it expects GDB to call a
7027 host system call on behalf of the target. GDB replies with an
7046 indicating what sort of thing the packet applies to. For example, GDB
7052 * Most GDB query and set packets have a leading upper case letter.
7070 GDB packet uses spaces to separate its components.
7075 Specify which operations GDB expects to request of the target, as
7079 is either 0, indicating that GDB will not request the operation,
7139 one or more thread IDs, separated by commas. GDB will respond to
7224 ELF `PT_LOAD' program headers), GDB will relocate entire
7228 GDB ignores this and instead applies the `Data' offset to the
7236 starting address of YYY. GDB will report an error if the
7278 do not need to stop the inferior, or be reported to GDB. All
7279 other signals should be reported to GDB. Multiple `QPassSignals'
7352 The stub has switched to no-acknowledgment mode. GDB
7353 acknowledges this reponse, but neither the stub nor GDB shall
7362 Tell the remote stub about features supported by GDB, and query
7363 the stub for features it supports. This packet allows GDB and the
7366 to improve GDB performance--a single larger packet performs better
7371 are not. These features must be reported before GDB will use
7374 under control with new versions of GDB which support increasing
7385 or that no features needed to be reported to GDB.
7403 The remote protocol feature NAME may be supported, and GDB
7409 set of GDB features should override any previous request. This
7410 allows GDB to put the stub in a known state, even if the stub had
7411 previously been communicating with a different version of GDB.
7413 The following values of GDBFEATURE (for the packet sent by GDB)
7417 This feature indicates whether GDB supports multiprocess
7418 extensions to the remote protocol. GDB does not use such
7424 This feature indicates that GDB supports the XML target
7430 This feature indicates whether GDB supports the `qRelocInsn'
7434 Stubs should ignore any unknown values for GDBFEATURE. Any GDB
7436 unlimited length (earlier versions of GDB may reject overly long
7438 the future to let the stub take advantage of new features in GDB,
7442 by GDB; first GDB describes all the features it supports, and then
7445 Similarly, GDB will silently ignore unrecognized stub feature
7452 Each feature has a default value, which GDB will use if
7494 length. GDB will send packets up to this size for bulk
7501 GDB guesses based on the size of the `g' packet response.
7569 extensions in packet replies unless GDB has also indicated it
7601 Notify the target that GDB is prepared to serve symbol lookup
7611 encoded). GDB may provide the value by using the
7620 SYM_VALUE (hex) is the value for symbol SYM_NAME. If GDB cannot
7629 encoded). GDB will continue to supply the values of symbols
7649 thinks is interesting for GDB to tell the user about the thread.
7650 The string is displayed in GDB's `info threads' display. Some
7873 the target process. Otherwise, GDB will omit the PID field and
7877 should be detached or killed when a GDB session is ended with the
7957 Here we describe the packets GDB uses to implement tracepoints (*note
8060 the conditional, and `cmd' for an action command. GDB sends a
8068 Although this packet is optional, and GDB will only send it if the
8080 encoded as hexadecimal values. GDB has the option of not using
8088 request packets from GDB.
8141 GDB uses this to mark read-only regions of memory, like those
8148 Set the choice to what to do with the tracing run when GDB
8151 if GDB is no longer in the picture.
8178 The trace stopped because GDB disconnected from the target.
8222 tracing will continue after GDB disconnects, `0' means that
8246 the target. GDB sends `qTfP' to get the first piece of data, and
8254 the target. GDB sends `qTfV' to get the first vari of data, and
8262 exist in the target program. GDB sends `qTfSTM' to get the first
8287 one or more markers, separated by commas. GDB will respond to each
8332 before the final result packet, to have GDB handle this relocation
8338 This requests GDB to copy instruction at address FROM to address
8340 the same effect as executing it at FROM. GDB writes the adjusted
8358 The "Host I/O" packets allow GDB to perform I/O operations on the far
8365 initiated by GDB, and the target's memory is not involved. *Note
8447 When a program on the remote target is running, GDB may attempt to
8449 `g', control of which is specified via GDB's `interrupt-sequence'.
8452 and may, in fact, be undefined. GDB does not currently define a
8454 which case GDB sends the `telnet' BREAK sequence.
8475 reply packets (*note Stop Reply Packets::) to GDB as a result of
8486 The GDB remote serial protocol includes "notifications", packets that
8487 require no acknowledgment. Both the GDB and the stub may send
8495 computed and formatted as for ordinary GDB packets. A notification's
8514 (Older versions of GDB ignore bytes received until they see the `$'
8517 notifications defined for GDB to send at the moment, but we assume that
8520 The following notification packets from the stub to GDB are defined:
8526 how these notifications are acknowledged by GDB.