Lines Matching full:command
89 * Interpreters:: Command Interpreters
99 * Command Line Editing:: Command Line Editing
351 command-line editing and command history.
357 enhanced the command-completion support to cover C++ overloaded symbols.
505 command.
510 Using the `run' command, we start `m4' running under GDB control; as
531 Now we use the command `n' (`next') to advance execution to the next
539 using the command `s' (`step') instead of `next'. `step' goes to the
550 the stack. We can use the `backtrace' command (which can also be
552 `backtrace' command displays a stack frame for each active subroutine.
582 quotes we specified. We use the command `p' (`print') to see their
592 the current line with the `l' (`list') command.
622 set them to better values using the `p' command, since it can print the
633 (`continue') command, and then try the example that caused trouble
653 command.
688 The command-line options described here are designed to cover a
710 Taking advantage of the second command-line argument requires a
721 command-line arguments (*note Arguments::) to `-O2 -c foo.c'.
728 You can further control how GDB starts up by using command-line
738 All options and command line arguments you give are processed in
795 Connect to process ID NUMBER, as with the `attach' command.
797 `-command FILE'
800 evaluated exactly as the `source' command would. *Note Command
801 files: Command Files.
803 `-eval-command COMMAND'
804 `-ex COMMAND'
805 Execute a single GDB command.
808 It may also be interleaved with `-command' as required.
838 command options and arguments have been processed. *Note Command
839 Files: Command Files.
849 command files specified with `-x' (and all commands from
852 the command files. Batch mode also disables pagination, sets
898 built in, then this option tells GDB to only use the command-line
945 Change interpretation of command line so that arguments following
946 the executable file are passed as command line arguments to the
965 source, assembly, registers and GDB command outputs (*note GDB
974 which communicate with GDB using it as a back end. *Note Command
985 This is equivalent to the `set write on' command inside GDB (*note
990 usage after it completes each command and returns to the prompt.
1012 1. Sets up the command interpreter as specified by the command line
1023 4. Processes command line options and operands.
1032 6. If the command line specified a program to debug, or a process to
1047 7. Reads command files specified by the `-x' option. *Note Command
1048 Files::, for more details about GDB command files.
1050 8. Reads the command history recorded in the "history file". *Note
1051 Command History::, for more details about the command history and
1054 Init files use the same syntax as "command files" (*note Command
1057 affect subsequent processing of command line options and operands.
1083 To exit GDB, use the `quit' command (abbreviated `q'), or type an
1089 terminates the action of any GDB command that is in progress and
1090 returns to GDB command level. It is safe to type the interrupt
1095 you can release it with the `detach' command (*note Debugging an
1106 `shell' command.
1108 `shell COMMAND STRING'
1109 Invoke a standard shell to execute COMMAND STRING. If it exists,
1112 `COMMAND.COM' on MS-DOS, etc.).
1115 do not have to use the `shell' command for this purpose in GDB:
1158 You can abbreviate a GDB command to the first few letters of the command
1161 get GDB to fill out the rest of a word in a command (or to show you the
1166 * Command Syntax:: How to give commands to GDB
1167 * Completion:: Command completion
1171 File: gdb.info, Node: Command Syntax, Next: Completion, Up: Commands
1173 3.1 Command Syntax
1176 A GDB command is a single line of input. There is no limit on how long
1177 it can be. It starts with a command name, which is followed by
1178 arguments whose meaning depends on the command name. For example, the
1179 command `step' accepts an argument which is the number of times to
1180 step, as in `step 5'. You can also use the `step' command with no
1183 GDB command names may always be truncated if that abbreviation is
1184 unambiguous. Other possible command abbreviations are listed in the
1189 to the `help' command.
1192 previous command. Certain commands (for example, `run') will not
1205 situation, GDB disables command repetition after any command that
1209 nothing. This is useful mainly in command files (*note Command Files:
1210 Command Files.).
1213 commands. This command accepts the current line, like <RET>, and then
1218 File: gdb.info, Node: Completion, Next: Help, Prev: Command Syntax, Up: Commands
1220 3.2 Command Completion
1223 GDB can fill in the rest of a word in a command for you, if there is
1225 are for the next word in a command, at any time. This works for GDB
1230 waits for you to finish the command (or press <RET> to enter it). For
1241 command, or backspace and enter something else, if `breakpoints' does
1242 not look like the command you expected. (If you were sure you wanted
1244 <RET> immediately after `info bre', to exploit command abbreviations
1245 rather than command completion).
1266 input (`b make_' in the example) so you can finish the command.
1309 Expressions: C Plus Plus Expressions. You can use the command `set
1351 the command `help'.
1377 Type "help" followed by command name for full
1379 Command name abbreviations are allowed if unambiguous.
1392 info -- Generic command for showing things
1394 show -- Generic command for showing things
1397 Type "help" followed by command name for full
1399 Command name abbreviations are allowed if unambiguous.
1402 `help COMMAND'
1403 With a command name as `help' argument, GDB displays a short
1404 paragraph on how to use that command.
1407 The `apropos' command searches through all of the GDB commands,
1421 The `complete ARGS' command lists all the possible completions for
1422 the beginning of a command. Use ARGS to specify the beginning of
1423 the command you want completed. For example:
1438 itself. Each command supports many topics of inquiry; this manual
1444 This command (abbreviated `i') is for describing the state of your
1459 using the related command `set'; for example, you can control what
1571 Use the `run' command to start your program under GDB. You must
1574 by using the `file' or `exec-file' command (*note Commands to
1600 `run' command. If a shell is available on your target, the shell
1615 the GDB working directory with the `cd' command in GDB. *Note
1621 in the `run' command line, or you can use the `tty' command to set
1630 When you issue the `run' command, your program begins to execute
1649 The `start' command does the equivalent of setting a temporary
1651 the `run' command.
1662 `start' command. These arguments will be given verbatim to the
1663 underlying `run' command. Note that the same arguments will be
1668 In these cases, using the `start' command would stop the execution
1679 shell command of the form `exec WRAPPER PROGRAM'. Quoting is
1696 This command is available when debugging locally on most targets,
1760 `run' command. They are passed to a shell, which expands wildcard
1772 `run', or those set by the `set args' command.
1810 `path' command. GDB replaces `.' in the DIRECTORY argument (with
1831 For example, this command:
1863 GDB with the `cd' command.
1878 the `/proc' support, you can use the `info proc' command (*note SVR4
1899 redirection with the `run' command. For example,
1906 is with the `tty' command. This command accepts a file name as
1917 An explicit redirection in `run' overrides the `tty' command's
1921 When you use the `tty' command or redirect input in the `run'
1922 command, only the input _for your program_ is affected. The input for
1926 You can use the `show inferior-tty' command to tell GDB to display
1943 This command attaches to a running process--one that was started
1945 command takes as argument a process ID. The usual way to find out
1947 the `jobs -l' shell command.
1950 executing the command.
1961 `file' command to load the program. *Note Commands to Specify Files:
1969 continue running, you may use the `continue' command after attaching
1974 the `detach' command to release it from GDB control. Detaching
1975 the process continues its execution. After the `detach' command,
1979 the command.
1982 process. If you use the `run' command, you kill that process. By
1985 `set confirm' command (*note Optional Warnings and Messages:
1997 This command is useful if you wish to debug a core dump instead of a
2003 `kill' command in this situation to permit running your program outside
2006 The `kill' command is also useful if you wish to recompile and
2060 To switch focus between inferiors, use the `inferior' command:
2071 the `remove-inferiors' command.
2078 command with the executable name as its argument.
2083 current inferior. This is a convenient command when you want to
2101 remove an inferior that is running with this command. For those,
2102 use the `kill' or `detach' command first.
2107 `detach inferior' command (allowing it to run independently), or kill it
2108 using the `kill inferiors' command:
2122 After the successful completion of a command such as `detach',
2133 The `set print inferior-events' command allows you to enable or
2149 command.
2159 with e.g., the `file' command.
2209 * `thread THREADNO', a command to switch among threads
2211 * `info threads', a command to inquire about existing threads
2213 * `thread apply [THREADNO] [ALL] ARGS', a command to apply a command
2229 `info threads', and always rejects the `thread' command, like this:
2233 Thread ID 1 not known. Use the "info threads" command to
2286 a Solaris-specific command:
2292 Make thread number THREADNO the current thread. The command
2309 breakpoint conditional expressions, command scripts, and so forth.
2313 `thread apply [THREADNO | all] COMMAND'
2314 The `thread apply' command allows you to apply the named COMMAND
2316 you want affected with the command argument THREADNO. It can be a
2319 numbers, as in `2-4'. To apply a command to all threads, type
2320 `thread apply all COMMAND'.
2323 This command assigns a name to the current thread. If no argument
2337 As well as being the complement to the `thread name' command, this
2338 command also allows you to identify a thread by its target SYSTAG.
2350 The `set print thread-events' command allows you to enable or
2441 process, use the command `set follow-fork-mode'.
2461 use the command `set detach-on-fork'.
2485 `info inferiors' command, and switch from one fork to another by using
2486 the `inferior' command (*note Debugging Multiple Inferiors and
2490 from it by using the `detach inferiors' command (allowing it to run
2491 independently), or kill it using the `kill inferiors' command. *Note
2502 If you issue a `run' command to GDB after an `exec' call executes,
2504 command with the parent executable name as its argument. By default,
2507 `set follow-exec-mode' command.
2539 with e.g., the `run' command, restarts the executable the
2556 You can use the `catch' command to make GDB stop whenever a `fork',
2588 The `checkpoint' command takes no arguments, but each checkpoint
2611 Note that breakpoints, GDB variables, command history etc. are
2677 as a signal, a breakpoint, or reaching a new line after a GDB command
2704 breakpoints with the `break' command and its variants (*note Setting
2719 breakpoints". You must use a different command to set watchpoints
2731 different command to set a catchpoint (*note Setting Catchpoints: Set
2734 `handle' command; see *note Signals: Signals.)
2746 `5-7'. When a breakpoint range is given to a command, all breakpoints
2757 * Break Commands:: Breakpoint command lists
2768 Breakpoints are set with the `break' command (abbreviated `b'). The
2797 command in the frame inside the selected frame--except that
2819 for the `break' command, and the breakpoint is set in the same
2826 `break' command and the breakpoint is set in the same way, but the
2837 reject this command if more than two are used. Delete or disable
2846 are the same as for the `hbreak' command and the breakpoint is set
2847 in the same way. However, like the `tbreak' command, the
2849 program stops there. Also, like the `hbreak' command, the
2856 REGEX. This command sets an unconditional breakpoint on all
2859 set with the `break' command. You can delete them, disable them,
2874 The `rbreak' command can be used to set breakpoints in *all* the
2923 string passed to the breakpoint command will be listed as it
2936 examining-address for the `x' command are set to the address of
2941 `ignore' command. You can ignore a large number of breakpoint
2989 command, where NUM is the number of the parent breakpoint, 1 in the
3022 when the `break' command cannot resolve breakpoint address
3042 The settings above only affect the `break' command and its variants.
3049 breakpoints set with the `break' command as well as to internal
3099 breakpoints with the GDB maintenance command `maint info breakpoints'
3154 changes. The simplest (and the most popular) use of this command
3159 If the command includes a `[thread THREADNUM]' clause, GDB breaks
3182 This command prints a list of watchpoints, using the same format as
3203 can-use-hw-watchpoints 0' command. With this variable set to zero, GDB
3219 When you issue the `watch' command, GDB reports
3230 with the `awatch' or `rwatch' command, it will print a message like
3297 shared library. Use the `catch' command to set a catchpoint.
3309 specified at the end of the command (eg `catch exception
3321 command to use to catch such exceptions is `catch exception
3351 each OS, so you can use the GDB command-line completion
3352 facilities (*note command completion: Completion.) to list the
3364 The example below illustrates how this command works if you
3468 Use the `info break' command to list the current catchpoints.
3523 With the `clear' command you can delete breakpoints according to
3524 where they are in your program. With the `delete' command you can
3557 you have `set confirm off'). You can abbreviate this command as
3584 with the `break' command starts out in this state.
3593 breakpoint set with the `tbreak' command starts out in this state.
3616 there. Breakpoints set by the `tbreak' command start out in this
3622 use one of the commands above. (The command `until' can set and delete
3661 (*note Breakpoint Command Lists: Break Commands.).
3664 `if' in the arguments to the `break' command. *Note Setting
3666 `condition' command.
3668 You can also use the `if' keyword with the `watch' command. The
3669 `catch' command does not recognize the `if' keyword; `condition' is the
3685 `condition' command (or a command that sets a breakpoint with a
3732 5.1.7 Breakpoint Command Lists
3741 `... COMMAND-LIST ...'
3753 single command, then the `commands' will apply to all the
3754 breakpoints set by that command. This applies to breakpoints set
3755 by `rbreak', and also applies when a single `break' command
3759 Pressing <RET> as a means of repeating the last GDB command is
3760 disabled within a COMMAND-LIST.
3763 Simply use the `continue' command, or `step', or any other command that
3766 Any other commands in the command list, after a command that resumes
3769 breakpoint--which could have its own command list, leading to
3772 If the first command you specify in a command list is `silent', the
3777 only at the beginning of a breakpoint command list.
3797 to any variables that need them. End with the `continue' command so
3798 that your program does not stop, and start with the `silent' command so
3815 command.
3818 This command saves all current breakpoint definitions together with
3822 To read the saved breakpoint definitions, use the `source' command
3823 (*note Command Files::). Note that watchpoints with expressions
3912 command you use). Either when continuing or when stepping, your
3950 source line, then stop it and return control to GDB. This command
3953 _Warning:_ If you use the `step' command while control is
3959 debugging information, use the `stepi' command, described
3962 The `step' command only stops at the first instruction of a source
3969 Also, the `step' command only enters a function if there is line
3971 `next' command. This avoids problems when using `cc -gl' on MIPS
3986 command. This command is abbreviated `n'.
3990 The `next' command only stops at the first instruction of a source
3996 The `set step-mode on' command causes the `step' command to stop
4005 Causes the `step' command to step over any functions which
4014 frame returns. Print the returned value (if any). This command
4017 Contrast this with the `return' command (*note Returning from a
4023 current stack frame, is reached. This command is used to avoid
4025 `next' command, except that when `until' encounters a jump, it
4031 until it exits the loop. In contrast, a `next' command at the end
4041 (`frame') command shows that execution is stopped at line `206';
4053 written before the body of the loop. The `until' command appeared
4066 command uses temporary breakpoints, and hence is quicker than
4087 upon exit from the current stack frame. This command is similar
4144 settings with the `handle' command.
4165 The keywords allowed by the `handle' command can be abbreviated.
4198 command with `pass' or `nopass' to control whether your program sees
4205 You can also use the `signal' command to prevent your program from
4221 You can see the data type using the `ptype $_siginfo' command. On Unix
4337 each with two threads, the `continue' command resumes only the two
4345 run with the `set schedule-multiple' command.
4349 resumed when an execution command is issued. When `on', all
4424 Suspending execution is done with the `interrupt' command when
4435 command interpreter, and it would be confusing if GDB unexpectedly
4436 changed to a different thread just as you entered a command to operate
4448 thread has stopped before prompting for another command. In background
4449 execution, GDB immediately gives a command prompt so that you can issue
4468 To specify background execution, add a `&' to the command. For
4469 example, the background form of the `continue' command is `continue&',
4505 execution command until the previous one finishes. Examples of
4510 by using the `interrupt' command.
4535 Use the qualifier `thread THREADNO' with a breakpoint command to
4626 `jump' command. It defaults to `on'.
4673 command will have no effect, nor will `Ctrl-c'. It defaults to
4721 Like the `step' command, `reverse-step' will only stop at the
4728 Also, as with the `step' command, if non-debuggable functions are
4746 just as the normal `next' command would take you from the last
4758 Just as the `finish' command takes you to the point where the
4770 `return' command cannot be used in reverse mode.
4831 This command starts the process record and replay target. The
4835 with the `target record' command.
4982 command (*note Information about a Frame: Frame Info.).
5037 The `frame' command allows you to move from one stack frame to
5043 The `select-frame' command allows you to move from one stack frame
5086 the threads, use the command `thread apply' (*note thread apply:
5098 Here is an example of a backtrace. It was made with the command `bt
5114 (integer, pointer, enumeration, etc). See command `set print
5245 After such a printout, the `list' command with no arguments prints
5256 GDB command scripts, where the output might be unnecessary and
5270 When used without any argument, this command does not change which
5273 argument, this command is used to select a stack frame. *Note
5278 This command prints a verbose description of the selected stack
5306 command. This requires the same kind of address (more than one
5307 for some architectures) that you specify in the `frame' command.
5339 source files by explicit command.
5360 To print lines from a source file, use the `list' command (abbreviated
5365 Here are the forms of the `list' command most commonly used:
5376 `list' command, this prints lines following the last lines
5385 the `list' command. You can change this using `set listsize':
5388 Make the `list' command display COUNT source lines (unless the
5394 Repeating a `list' command with <RET> discards the argument, so it
5400 In general, the `list' command expects you to supply zero, one or two
5412 When a `list' command has two linespecs, and the source file of
5451 line". For the `list' command, the current line is the last one
5455 the second of the two linespecs in a `list' command, this
5524 To edit the lines in a source file, use the `edit' command. The
5534 LOCATION argument; here are the forms of the `edit' command most
5563 the following command-line syntax:
5579 The command `forward-search REGEXP' checks each line, starting
5582 `search REGEXP' or abbreviate the command name as `fo'.
5585 The command `reverse-search REGEXP' checks each line, starting
5588 abbreviate this command as `rev'.
5630 in that order. To add other directories, use the `directory' command.
5633 script files (read using the `-command' option and `source' command).
5652 path substitution rule, use the `set substitute-path' command (*note
5664 command. However, `set substitute-path' can be more efficient in the
5666 subdirectories. With the `directory' command, you need to add each
5669 you to direct the debugger to all the sources with one single command.
5671 `set substitute-path' is also more than just a shortcut command.
5692 directory names may be given to this command, separated by `:'
5723 `/mnt/cross/baz.c', then the command
5770 directories in one command.
5778 You can use the command `info line' to map source lines to program
5779 addresses (and vice versa), and the command `disassemble' to display a
5780 range of addresses as machine instructions. You can use the command
5783 line' command causes the arrow to point to the line specified. Also,
5802 After `info line', the default address for the `x' command is
5811 This specialized command dumps a range of memory as machine
5816 the selected frame. A single argument to this command is a
5903 Currently this command is only defined for the Intel x86 family.
5935 command (abbreviated `p'), or its synonym `inspect'. It evaluates and
5956 A more low-level way of examining data is with the `x' command. It
5961 fields of a struct or a class are declared, use the `ptype EXP' command
6004 syntax is {ELEMENT, ELEMENT...}. For example, you can use the command
6063 current command. If the command in which the expression was used
6085 Use the "delete" command to delete unwanted
6093 By default, MODE is set to `all'. If the command with which the
6107 error due to the ambiguity and the command is aborted.
6301 `print' command with a slash and a format letter. The format letters
6328 The command `info symbol 0x54320' yields similar results. *Note
6367 Note that no space is required before the slash; this is because command
6371 format, you can use the `print' command with just a format and no
6377 with the `x' command, where `b' stands for "byte"; see *note Examining
6386 You can use the command `x' (for "examine") to examine memory in any of
6392 Use the `x' command to examine memory.
6464 For convenience, especially when used with the `display' command, the
6467 is within the count. The command `disassemble' gives an alternative
6475 `x/7'. If you use <RET> to repeat the `x' command, the repeat count N
6489 The addresses and contents printed by the `x' command are not saved
6493 `$_' and `$__'. After an `x' command, the last address examined is
6498 If the `x' command has a repeat count, the address and contents saved
6506 downloaded to the target. The `compare-sections' command is provided
6513 With no arguments, compares all loadable sections. This command's
6565 numbers of the displays that you want affected with the command
6577 want affected with the command argument DNUMS. It can be a single
6586 affected with the command argument DNUMS. It can be a single
6606 variables is not defined. For example, if you give the command
6740 command. This limit also applies to the display of strings. When
6749 This command allows to control how the values of arguments are
6773 By default, only scalar arguments are printed. This command can
7017 The `info pretty-printer' command will list all the installed
7162 Values printed by the `print' command are saved in the GDB "value
7192 command--which you can do by just typing <RET>.
7200 then the value recorded in the value history by the `print' command
7265 in a command script.
7277 Repeat that command by typing <RET>.
7283 The variable `$_' is automatically set by the `x' command to the
7288 by the `x' command, in which case it is a pointer to the type of
7292 The variable `$__' is automatically set by the `x' command to the
7310 example, it will be empty before you execute the `run' command.
7380 command shows the canonical names. For example, on the SPARC, `info
7400 sense for your program), but the `info registers' command prints the
7487 user', for this interface. You can use the command `info udot' to
7494 `examine' command.
7524 target does not return a list of possible types, this command will
7530 command corresponding to the process.
7681 write data to a file, and the `restore' command reads data from a file
7716 command can automatically recognize any known BFD file format,
7748 special command for that.
7757 Note that this command is implemented only for some systems (as of
7777 you give GDB the command `set target-charset EBCDIC-US', then GDB
7783 command, described below.
7797 `set host-charset' command. On some systems, GDB cannot
7860 We can use the `show charset' command to see what character sets GDB
7956 Mode::) memory can be changed _while_ a gdb command is executing.
7981 referenced. This command is useful for debugging the data cache
8017 `find' command.
8148 inlined by using the `info frame' command.
8190 the `finish' command. This is a limitation of compiler-generated
8234 (This command is not yet implemented.) Show the results of
8237 expansion are left unchanged. This command allows you to see the
8245 source location or compiler command-line where that definition was
8252 REPLACEMENT-LIST. The first form of this command defines an
8257 A definition introduced by this command is in scope in every
8259 undef' command, described below. The definition overrides all
8265 This command only affects definitions provided with the `macro
8266 define' command, described above; it cannot remove definitions
8270 List all the macros defined using the `macro define' command.
8389 compilation command line using the `-DNAME=VALUE' syntax. For macros
8415 using the `tfind' command, you can examine the values those expressions
8515 The `trace' command is very similar to the `break' command. Its
8518 `trace' command defines a tracepoint, which is a point in the
8522 next `tstart' command, and once a trace experiment is running,
8526 Here are some examples of using the `trace' command:
8548 The `ftrace' command sets a fast tracepoint. For targets that
8553 the desired location, in which case the command will exit with an
8559 The `strace' command sets a static tracepoint. For targets that
8563 which case the command will exit with an explanatory message.
8570 the `ID' field of the `info static-tracepoint-markers' command
8599 Note that `info static-tracepoint-markers' command output lists
8612 `delete' command can remove tracepoints also.
8620 You can abbreviate this command as `del tr'.
8635 disabled tracepoint using the `enable tracepoint' command.
8653 tracepoint number NUM is not specified, the `passcount' command
8690 using `if' in the arguments to the `trace' command. *Note Setting
8692 changed at any time with the `condition' command, just as with
8703 could use the following tracepoint command to collect data about calls
8721 `tvariable' command
8737 The `tvariable' command creates a new trace state variable named
8739 EXPRESSION is evaluated when this command is entered; the result
8741 report an error. A subsequent `tvariable' command specifying the
8764 This command will prompt for a list of actions to be taken when the
8766 this command sets the actions for the one that was most recently
8775 Command Lists: Break Commands.), except that only the defined
8776 actions are allowed; any other GDB command is rejected.
8790 following the tracepoint, a `while-stepping' command is used,
8792 sequence of single steps. The `while-stepping' command is
8793 terminated by its own separate `end' command. Lastly, the action
8794 list is terminated by an `end' command.
8808 This command accepts a comma-separated list of any valid
8840 a single argument, or one `collect' command with several arguments
8843 The command `info scope' (*note info scope: Symbols.) is
8848 command accepts a comma-separated list of expressions. The results
8856 collecting new data after each step. The `while-stepping' command
8858 (followed by its own `end' command):
8895 command, simply restricting itself to tracepoints.
8900 * its passcount as given by the `passcount N' command
8913 This command can be abbreviated `info tp'.
8974 This command takes no arguments. It starts the trace experiment,
8980 This command takes no arguments. It ends the trace experiment, and
8988 This command displays the status of the current trace data
9119 wish to capture). Then the `backtrace' command will show a
9169 The basic command for selecting a trace snapshot from the buffer is
9173 Here are the various forms of using the `tfind' command.
9225 giving one `tfind' command, and then simply hitting <RET> repeatedly
9228 reverse order. The `tfind line' command with no argument selects the
9229 snapshot for the next source line executed. The `tfind pc' command with
9231 (PC) as the current frame. The `tfind tracepoint' command with no
9279 This command takes no arguments. It prints all the data collected at
9350 This command saves all current tracepoint definitions together with
9353 definitions, use the `source' command (*note Command Files::). The
9354 `save-tracepoints' command is a deprecated alias for `save tracepoints'
9404 data, via the `target tfile' command.
9407 Save the trace data to FILENAME. By default, this command assumes
9615 so this command should only be necessary if you have changed the
9616 overlay mapping yourself using GDB. This command is only useful
9672 auto' command (*note Overlay Commands::), GDB looks in the inferior's
9805 language' command for either purpose. On startup, GDB defaults to
9891 the command `set language LANG', where LANG is the name of a language,
9900 written in C, and GDB was parsing Modula-2, a command such as:
9987 command, for example. As with the working language, GDB can also
10169 command-line options `-gdwarf-2' and `-gstabs+'. *Note Options for
10425 The GDB command-completion facility can simplify this; see *note
10426 Command Completion: Completion.
10575 use the GDB command-line word completion facilities to list the
10577 Command Completion: Completion, for details on how to do this.
10624 This section provides information about some commands and command
10632 * The Print Command with Objective-C::
10635 File: gdb.info, Node: Method Names in Commands, Next: The Print Command with Objective-C, Up: Objective-C
10690 File: gdb.info, Node: The Print Command with Objective-C, Prev: Method Names in Commands, Up: Objective-C
10692 15.4.3.2 The Print Command With Objective-C
10695 The print command has also been extended to accept methods. For
10701 result. Also, an additional command has been added, `print-object' or
10703 However, this command may only work with certain Objective-C libraries
10803 the `set case-insensitive' command, see *note Symbols::, for the
10816 This command prints the values contained in the Fortran `COMMON'
10832 The Pascal-specific command `set print pascal_static-members'
11420 mostly for documenting command files. The standard GDB comment (`#')
11429 the `call' command, and functions to procedures elsewhere.
11650 This command shows a list of current Ada tasks, as in the
11730 This command shows detailled informations on the specified task,
11745 This command prints the ID of the current task.
11755 This command is like the `thread THREADNO' command (*note
11775 These commands are like the `break ... thread ...' command (*note
11779 Use the qualifier `task TASKNO' with a breakpoint command to
11831 with read-write privileges, using the command `"set write on"' (*note
11854 working properly. To be effective, this command should be run
11970 Occasionally, you may wish to control that. The command `set
11979 This command shows the current setting of case sensitivity for
12000 This is the opposite of the `info address' command. You can use
12072 This command differs from `ptype' in two ways: first, like
12077 List all the variables local to a particular scope. This command
12093 This command
12200 The `set print symbol-loading' command allows you to enable or
12219 command `info sources' to find out which files these are. If you
12317 the `set' command instead of the `print' command. `set' is really the
12322 If the beginning of the argument string of the `set' command appears
12323 identical to a `set' subcommand, use the `set variable' command instead
12324 of just `set'. This command is identical to `set' except for its lack
12327 width=13', because GDB has the command `set width':
12341 Because the `set' command has many subcommands that can conflict
12343 variable' command instead of just `set'. For example, if your program
12345 with just `set g=4', because GDB has the command `set gnutarget',
12391 it stopped, with the `continue' command. You can instead continue at
12400 `tbreak' command in conjunction with `jump'. *Note Setting
12403 The `jump' command does not change the current stack frame, or the
12409 command requests confirmation if the specified line is not in the
12415 command by storing a new value into the register `$pc'. The difference
12421 makes the next `continue' command or stepping command execute at
12425 The most common occasion to use the `jump' command is to back
12444 with the `continue' command; `signal 0' causes it to resume
12448 executing the command.
12450 Invoking the `signal' command is not the same as invoking the `kill'
12453 tables (*note Signals::). The `signal' command passes the signal
12465 command. If you give an EXPRESSION argument, its value is used as
12479 The `return' command does not resume execution; it leaves the
12481 returned. In contrast, the `finish' command (*note Continuing and
12543 You can use this variant of the `print' command if you want to
12550 command to generate a signal (e.g., if there's a bug in the function,
12552 controlled by the `set unwindonsignal' command.
12555 call via the `print' or `call' command to generate an exception that is
12561 controlled by the `set unwind-on-terminating-exception' command.
12606 explicitly with the `set write' command. For example, you might want
12616 the `exec-file' or `core-file' command) after changing `set
12661 program executed when you use the `run' command. If you do not
12666 both GDB and your program, using the `path' command.
12669 command. You will not be able to "run" an object file, but you
12689 searched when necessary. Use the `file' command to get both symbol
12695 The `symbol-file' command causes GDB to forget the contents of
12713 systems using COFF, the `symbol-file' command does not normally
12722 source file are being read. (The `set verbose' command can turn
12753 `kill' command (*note Killing the Child Process: Kill Process.).
12758 The `add-symbol-file' command reads additional symbol table
12759 information from the file FILENAME. You would use this command
12769 originally read with the `symbol-file' command. You can use the
12770 `add-symbol-file' command any number of times; the new symbol data
12772 instead, use the `symbol-file' command without any arguments.
12788 loaded, and provide these to the `add-symbol-file' command.
12811 header. For this command to work, you must have used
12816 The `add-shared-symbol-files' command can currently be used only
12818 for the `dll-symbols' command (*note Cygwin Native::). GDB
12825 The `section' command changes the base address of the named
12830 command, described below, lists all the sections and their
12839 loaded. The command `help target' lists all possible targets
12843 Another command that can give you extra information about program
12845 information displayed by `info files', this command displays the
12848 following command options (which may be arbitrarily combined):
12930 when you use the `run' command, or when you examine a core file.
12931 (Before you issue the `run' command, GDB does not understand references
12951 command. The default value is `on'.
12966 command:
12990 command for this:
12993 This command controls whether GDB should give you control when the
13027 when using a remote target that supports the `remote get' command
13073 The `set solib-absolute-prefix' command is an alias for `set
13200 command-line option in *note Command Line Options:
13294 * The debug link method needs the following additional command to
13300 contains a version of the `strip' command such that the command
13302 `objcopy' commands and the `ln -s' command above, together.
13419 To create an index file, use the `save gdb-index' command:
13450 many times the problems occur, with the `set complaints' command (*note
13543 command line option. *Note Mode Options::.
13558 command to specify one of the
13564 available architectures with the `set architecture' command.
13567 This command sets the current target architecture to ARCH. The
13605 command (*note Debugging an Already-running Process: Attach.).
13623 The `target' command does not repeat if you press <RET> again
13624 after executing the command.
13639 command. Unlike most `target' commands, with `gnutarget' the
13648 Use the `show gnutarget' command to display what file format
13666 connection. This command tells GDB to use its own remote protocol
13674 `target remote' supports the `load' command. This is only useful
13706 This command controls whether a hash mark `#' is displayed while
13724 GDB, the `load' command may be available. Where it exists, it is
13728 `add-symbol-file' command.
13730 If your GDB does not have a `load' command, attempting to execute
13818 packets varies. The `target remote' command establishes a connection
13828 `--baud' option, or use the `set remotebaud' command (*note set
13829 remotebaud: Remote Configuration.) before the `target' command.
13863 `target remote | COMMAND'
13864 Run COMMAND in the background and communicate with it using a
13865 pipe. The COMMAND is a shell command, to be parsed and expanded
13866 by the system's command shell, `/bin/sh'; it should expect remote
13872 If COMMAND closes its standard output (perhaps by exiting), GDB
13897 the `detach' command to release it from GDB control. Detaching
13900 command, GDB is free to connect to another target.
13903 The `disconnect' command behaves like `detach', except that the
13906 the `disconnect' command, GDB is again free to connect to another
13910 This command allows you to send arbitrary commands directly to the
13912 sends like this, this command is the way to extend GDB--you can
14009 `target remote' command.
14042 or attach to a new program. The `run' command uses `set remote
14044 Command line arguments are supported, except for wildcard expansion and
14047 To start `gdbserver' without supplying an initial command to run or
14048 process ID to attach, use the `--multi' command line option. Then you
14056 20.3.1.3 Other Command-Line Arguments for `gdbserver'
14067 then any command-line arguments to pass to the wrapper, then `--'
14071 command line including the wrapper arguments, then the name of the
14092 for your application using the `file' command before you connect. Use
14106 to using the `target remote' command. Otherwise you may get an error
14108 something like `Connection refused'. Don't use the `load' command in
14115 command to send special requests to `gdbserver'. Here are the
14131 When this command is issued, PATH is a colon-separated list of
14140 Tell gdbserver to exit immediately. This command should be
14170 `-linproctrace' to the link command.
14178 `--wrapper' command line option.
14185 `call' command for that. For example:
14213 process; you can confirm it with the `info sharedlibrary' command,
14367 For each packet NAME, the command to enable or disable the packet is
14370 Command Name Remote Packet Related Features
14463 else is set up, you can simply use the `target remote' command
14532 GDB needs, until you execute a GDB command that makes your program
14756 Set current context from proc address. This command isn't
14768 system with this facility, the command `info proc' is available to
14781 command line used to invoke it, its current working directory, and
14812 This command enables and disables tracing of `procfs' API calls.
14833 For QNX Neutrino only, this command displays the list of all the
14837 For QNX Neutrino only, this command displays the list of all
14860 This command displays assorted information about the underlying
14910 `info dos pde' command means display only that entry from the Page
14911 Directory table. An argument given to the `info dos pte' command
14922 This command displays the Page Table entry for a specified linear
14925 because this command accepts addresses which may belong to _any_
14959 This command is supported only with some DPMI servers.
14966 This command sets the base I/O port address of the `COM1' serial
14970 This command sets the "Interrupt Request" (`IRQ') line to use for
14982 This command prints the status of the 4 DOS serial ports. For each
15011 This command displays information returned by the Win32 API
15014 this given selector. Without argument, this command displays
15018 This command displays thread specific information stored in the
15026 This command loads symbols from a dll similarly to add-sym command
15107 library information in *note Files::, or the `dll-symbols' command in
15162 type information in the command. Here's an example of the type of
15207 This command toggles the state of inferior signal interception by
15209 by this command. `sigs' is a shorthand alias for `signals'.
15217 This command tells GDB which thread is the `libc' signal thread.
15233 This command shows whether GDB thinks the debuggee is stopped.
15236 Use this command to turn off trapping of exceptions in the
15245 This command toggles task suspension when GDB has control.
15256 This command sets the suspend count the task will be left with when
15264 This command sets the task exception port to which GDB will
15269 This command switches GDB to a mode that is the least invasive as
15287 This command toggles current thread suspension when GDB has
15291 Normally, this command has no effect, since when GDB has control,
15293 off' (see above), this command comes in handy to suspend only the
15297 This command shows the state of current thread suspension.
15300 This command sets whether the current thread is allowed to run.
15306 This command sets the suspend count GDB will leave on a thread
15322 GDB finds when it notices each thread. This command changes the
15368 more verbose output. This is a command to diagnose problems
15377 then mapped to a Posix signal. Use this command to turn on
15464 The GDB command `target' lets you connect to a VxWorks target on the
15476 these files by searching the directories listed in the command search
15483 with the GDB command `path', and execute the `target' command again.
15492 object that has not yet been loaded, you can use the GDB `load' command
15494 given as an argument to the `load' command is actually opened twice:
15517 You can also use the `load' command to reload an object module after
15530 You can also attach to an existing task using the `attach' command as
15549 to send an arbitrary command to the simulator.
15551 `sim COMMAND'
15552 Send an arbitrary COMMAND string to the simulator. Consult the
15598 This command toggles ARM operation mode between 32-bit and 26-bit.
15604 This command sets the ARM floating-point unit (FPU) type. The
15627 This command forces GDB to use the specified ABI.
15634 instructions are ARM or Thumb. This command controls GDB's
15643 This command overrides use of the symbol table to determine whether
15677 (the default), vector catching is enabled. For this command to
15679 command.
15749 Test the `upload' command.
15754 This command resets the SDI connection.
15757 This command shows the SDI connection status.
15783 command for the following ROM monitor.
15810 Use this command to connect to the target if you are running GDB
15814 Use this command to connect to the target if it is connected to
15818 Use this command to download a program to the MicroBlaze target.
15842 command `target mips PORT', where PORT is the name of the serial
15844 downloaded to the board, you may use the `load' command to
15887 coprocessor, you should use the command `set mipsfpu none' (if you
15888 need this, you may wish to put the command in your GDB init file).
15894 the command `set mipsfpu single'. The default double precision
15910 the MIPS remote protocol, with the `set timeout SECONDS' command.
15913 retransmit-timeout SECONDS' command. The default is 3 seconds.
15957 `pmon COMMAND'
15958 This command allows sending an arbitrary COMMAND string to the
15977 `or1ksim COMMAND'
16100 command.
16156 `sds COMMAND'
16157 Send the specified COMMAND string to the SDS monitor.
16221 The GDB command `file' lets you choose with program to debug.
16226 the file by searching the directories listed in the command search path.
16237 command again.
16245 The GDB command `target' lets you connect to a Sparclet target. To
16263 command to download the file from the host to the target. The file
16264 name and load offset should be given as arguments to the `load' command.
16307 You must use an additional command to debug the program. For
16331 `file' command to load a new program image, the `run' command to run
16362 This command displays information about the AVR I/O registers. For
16376 CRIS version affects register names and sizes. This command is
16476 stack with the `set rstack_high_address' command. The argument
16513 command when debugging a stripped executable.
16554 This command determines whether the most-significant 32 bits of
16564 This command controls compatibility with 64-bit MIPS targets that
16574 This command turns on and off debugging messages for the
16590 This command determines whether HPPA architecture-specific
16597 This command displays the contents of the unwind table entry at the
16685 command. For commands controlling how GDB displays data, see *note
16691 * Editing:: Command editing
16692 * Command History:: Command history
16706 GDB indicates its readiness to read a command by printing a string
16708 the prompt string with the `set prompt' command. For instance, when
16723 File: gdb.info, Node: Editing, Next: Command History, Prev: Prompt, Up: Controlling GDB
16725 22.2 Command Editing
16730 command line interface to the user. Advantages are GNU Emacs-style or
16732 and a storage and recall of command history across debugging sessions.
16734 You may control the behavior of command line editing in GDB with the
16735 command `set'.
16739 Enable command line editing (enabled by default).
16742 Disable command line editing.
16745 Show whether command line editing is enabled.
16747 *Note Command Line Editing::, for more details about the Readline
16752 File: gdb.info, Node: Command History, Next: Screen Size, Prev: Editing, Up: Controlling GDB
16754 22.3 Command History
16759 these commands to manage the GDB command history facility.
16765 To issue a command to GDB without affecting certain aspects of the
16767 Prefix::). This means that this command will not affect the command
16768 history, nor will it affect GDB's notion of which command to repeat if
16773 history, use the `output' command instead of the `print' command.
16775 Here is the description of GDB commands related to command history.
16778 Set the name of the GDB command history file to FNAME. This is
16779 the file where GDB reads an initial command history list, and
16780 where it writes the command history from this session when it
16782 through the history command editing characters listed below. This
16789 Record command history in a file, whose name may be specified with
16790 the `set history filename' command. By default, this option is
16794 Stop recording command history in a file.
16806 `set history expansion on' command, you may sometimes need to follow
16830 Display the last ten commands in the command history.
16833 Print ten commands centered on command number N.
16839 File: gdb.info, Node: Screen Size, Next: Numbers, Prev: Command History, Up: Controlling GDB
16948 override its conclusion using the `set osabi' command. One example
17014 on a slow machine, you may want to use the `set verbose' command. This
17070 find it useful to enable "command tracing". In this mode each command
17072 symbols, the quantity denoting the call depth of each command.
17075 Enable command tracing.
17078 Disable command tracing.
17081 Display the current state of command tracing.
17097 asynchronous command finishes its execution. The default is off.
17100 Displays the current setting of asynchronous command completion
17253 target or use the `run' command.
17290 answer queries generated by commands entered at the command
17320 treated as a GDB Command Files. *Note Command files: Command Files.
17326 All scripts are always evaluated as GDB Command Files.
17332 as a GDB Command File.
17354 Aside from breakpoint commands (*note Breakpoint Command Lists: Break
17356 execution as a unit: user-defined commands and command files.
17362 * Command Files:: How to write scripts of commands to be stored in a file
17371 A "user-defined command" is a sequence of GDB commands to which you
17372 assign a new name as a command. This is done with the `define'
17373 command. User commands may accept up to 10 arguments separated by
17374 whitespace. Arguments are accessed within the user command via
17381 To execute the command use:
17385 This defines the command `adder', which prints the sum of its three
17403 Define a command named COMMANDNAME. If there is already a command
17405 it. COMMANDNAME may be a bare command name consisting of letters,
17407 predefined prefix command. For example, `define target my-target'
17408 creates a user-defined `target my-target' command.
17410 The definition of the command is made up of other GDB command
17411 lines, which are given following the `define' command. The end of
17415 Document the user-defined command COMMANDNAME, so that it can be
17416 accessed by `help'. The command COMMANDNAME must already be
17417 defined. This command reads lines of documentation just as
17418 `define' reads the lines of the command definition, ending with
17419 `end'. After the `document' command is finished, `help' on command
17422 You may use the `document' command again to change the
17423 documentation of a command. Redefining the command with `define'
17427 Used inside a user-defined command, this tells GDB that this
17428 command should not be repeated when the user hits <RET> (*note
17429 repeat last command: Command Syntax.).
17445 infinite recursion and aborts the command.
17448 use control flow commands, described in *note Command Files::.
17451 definition are not printed. An error in any command stops execution of
17452 the user-defined command.
17455 proceed without asking when used inside a user-defined command. Many
17457 omit the messages when used in a user-defined command.
17460 File: gdb.info, Node: Hooks, Next: Command Files, Prev: Define, Up: Sequences
17462 23.1.2 User-defined Command Hooks
17466 command. Whenever you run the command `foo', if the user-defined
17467 command `hook-foo' exists, it is executed (with no arguments) before
17468 that command.
17470 command you
17471 executed. Whenever you run the command `foo', if the user-defined
17472 command `hookpost-foo' exists, it is executed (with no arguments) after
17473 that command. Post-execution hooks may exist simultaneously with
17474 pre-execution hooks, for the same command.
17476 It is valid for a hook to call the command which it hooks. If this
17480 In addition, a pseudo-command, `stop' exists. Defining
17501 command, and to add extra text to the beginning and end of the message,
17516 You can define a hook for any single-word command in GDB, but not
17517 for command aliases; you should define a hook for the basic command
17519 command by adding `hook-' or `hookpost-' to the last word of the
17520 command, e.g. `define target hook-remote' to add a hook to `target
17524 GDB commands stops and GDB issues a prompt (before the command that you
17527 If you try to define a hook which does not match any known command,
17528 you get a warning from the `define' command.
17531 File: gdb.info, Node: Command Files, Next: Output, Prev: Hooks, Up: Sequences
17533 23.1.3 Command Files
17536 A command file for GDB is a text file made of lines that are GDB
17538 empty line in a command file does nothing; it does not mean to repeat
17539 the last command, as it would from the terminal.
17541 You can request the execution of a command file with the `source'
17542 command. Note that the `source' command is also used to evaluate
17543 scripts that are not Command Files. The exact behavior can be
17548 Execute the command file FILENAME.
17550 The lines in a command file are generally executed sequentially,
17553 executed. An error in any command terminates execution of the command
17559 with the `directory' command); except that `$cdir' is not searched
17575 If `-v', for verbose mode, is given then GDB displays each command
17580 proceed without asking when used in a command file. Many GDB commands
17582 messages when called from command files.
17584 GDB also accepts command input from standard input. In this mode,
17586 error. Errors in a command file supplied on standard input do not
17587 terminate execution of the command file--execution continues with the
17588 next command.
17596 Since commands stored on command files tend to be more general than
17607 This command allows to include in your script conditionally
17608 executed commands. The `if' command takes a single argument, which
17617 This command allows to write loops. Its syntax is similar to
17618 `if': the command takes a single argument, which is an expression
17625 This command exits the `while' loop in whose body it is included.
17629 This command skips the execution of the rest of the body of
17639 File: gdb.info, Node: Output, Prev: Command Files, Up: Sequences
17644 During the execution of a command file or a user-defined command, normal
17658 the command `echo \ and foo = \ '.
17661 the command onto subsequent lines. For example,
17757 the string TEMPLATE to a command line, and call it.
17790 GDB provides one command for accessing the Python interpreter, and one
17794 The `python' command can be used to evaluate Python code.
17796 If given an argument, the `python' command will evaluate the
17797 argument as a Python command. For example:
17803 multi-line command, like `define'. In this case, the Python
17804 script is made up of subsequent command lines, given after the
17805 `python' command. This command list is terminated using a line
17879 `python' command.
17884 -- Function: execute command [from_tty] [to_string]
17885 Evaluate COMMAND, a string, as a GDB CLI command. If a GDB
17886 exception happens while COMMAND runs, it is translated as
17889 FROM_TTY specifies whether GDB ought to consider this command as
17893 By default, any output produced by COMMAND is sent to GDB's
17933 This function can be useful when implementing a new command (*note
17934 Commands In Python::), as it provides a way to parse the command's
18045 When executing the `python' command, Python exceptions uncaught within
18047 mechanism. If the command that called `python' does not handle the
18081 When implementing GDB commands in Python via `gdb.Command', it is
18083 to be printed. For example, the user may have invoked the command
18088 >class HelloWorld (gdb.Command):
18980 obtained by running the command `info signals' in the
18981 GDB command prompt.
19063 You can implement new GDB CLI commands in Python. A CLI command is
19064 implemented using an instance of the `gdb.Command' class, most commonly
19067 -- Method on Command: __init__ name COMMAND_CLASS [COMPLETER_CLASS]
19069 The object initializer for `Command' registers the new command
19073 NAME is the name of the command. If NAME consists of multiple
19081 below. This argument tells GDB how to categorize the new command
19086 tells GDB how to perform completion for this command. If not
19091 PREFIX is an optional argument. If `True', then the new command
19092 is a prefix commandcommand may be
19095 The help text for the new command is taken from the Python
19096 documentation string for the command's class, if there is one. If
19098 command is not documented." is used.
19100 -- Method on Command: dont_repeat
19101 By default, a GDB command is repeated when the user enters a blank
19102 line at the command prompt. A command can suppress this behavior
19104 command `dont-repeat', see *note dont-repeat: Define.
19106 -- Method on Command: invoke argument from_tty
19107 This method is called by GDB when this command is invoked.
19109 ARGUMENT is a string. It is the argument to the command, after
19113 command was entered by the user at the terminal; when false it
19114 means that the command came from elsewhere.
19129 -- Method on Command: complete text word
19131 this command. All forms of completion are handled by this method,
19133 and the `complete' command (*note complete: Help.).
19136 complete command line up to the cursor's location. WORD holds the
19137 last word of the command line; this is computed using a
19155 When a new command is registered, it must be declared as a member of
19159 command. The available classifications are represented by constants
19163 The command does not belong to any particular class. A command in
19167 The command is related to running the inferior. For example,
19173 The command is related to data or variables. For example, `call',
19178 The command has to do with manipulation of the stack. For example,
19197 The command is an `info'-related command, that is, related to the
19203 The command has to do with breakpoints. For example, `break',
19209 The command has to do with tracepoints. For example, `trace',
19215 The command is only used in unusual circumstances, or is not of
19221 The command is only useful to GDB maintainers. The `maintenance'
19226 A new command can use a predefined completion function, either by
19242 This constant means that completion should examine GDB command
19249 The following code snippet shows how a trivial CLI command can be
19252 class HelloWorld (gdb.Command):
19264 registration of the command with GDB. Depending on how the Python code
19285 -- Method on Parameter: __init__ name COMMAND-CLASS PARAMETER-CLASS
19301 COMMAND-CLASS should be one of the `COMMAND_' constants (*note
19322 as the help text for this parameter's `set' command. The value is
19328 as the help text for this parameter's `show' command. The value is
19947 contents can be any location recognized by the `break' command, or
19948 in the case of a watchpoint, by the `watch' command. The optional
19955 be listed with the `maint info breakpoints' command). The
20019 the first command is `silent'. This is not reported by the
20049 when set, or when the `info breakpoints' command is run. This
20154 When a new object file is read (for example, due to the `file' command,
20394 24 Command Interpreters
20397 GDB supports multiple command interpreters, and some command
20401 GDB currently supports two command interpreters, the console
20402 interpreter (sometimes called the command-line interpreter or CLI) and
20412 The traditional console or command-line interpreter. This is the
20430 situation. Consider an IDE using GDB/MI. If a user enters the command
20436 using the appropriate command. If you are running the console
20437 interpreter, simply use the `interpreter-exec' command:
20441 GDB/MI has a similar command, although it is only available in
20478 This window is the GDB command window with the GDB prompt and the
20521 These windows are not all visible at the same time. The command
20535 A status line above the command window shows the following
20566 Command Line Editing::). The following key bindings are installed for
20596 command gives the focus to the next TUI window.
20628 are not available for their normal use by readline unless the command
20631 control the command window.
20673 Other keys temporarily switch to the GDB command prompt. The key
20676 SingleKey mode. Once the command is entered the TUI SingleKey mode is
20735 Make the command window active for scrolling.
20823 To use this interface, use the command `M-x gdb' in Emacs. Give the
20824 executable file you want to debug as an argument. This command starts
20857 We call this "text command mode". Emacs 22.1, and later, also uses
20880 Emacs variable `gud-gdb-command-name' to run the one you want.
20889 Execute to another source line, like the GDB `step' command; also
20894 calls, like the GDB `next' command. Then update the display window
20898 Execute one instruction, like the GDB `stepi' command; update
20903 `finish' command.
20907 command.
20912 command.
20916 like the GDB `down' command.
20918 In any source file, the Emacs command `C-x <SPC>' (`gud-break')
20921 In text command mode, if you type `M-x speedbar', Emacs displays a
20930 get it back is to type the command `f' in the GDB buffer, to request a
20954 activated by specifying using the `--interpreter' command line option
20987 * GDB/MI Command Syntax::
20992 * GDB/MI Command Description Format::
21008 File: gdb.info, Node: GDB/MI General Design, Next: GDB/MI Command Syntax, Up: GDB/MI
21015 notifications. Each command results in exactly one response,
21016 indicating either successful completion of the command, or an error.
21022 command and reported as part of that command response.
21031 know whether the resuming command itself was successfully executed.
21037 including this information in command response would mean no
21038 output is produced until the command is finished, which is
21043 example, a command may change the selected thread. Although such
21044 changes can be included in command response, using notification
21048 There's no guarantee that whenever an MI command reports an error,
21050 is not reverted to the state before the MI command was processed.
21051 Therefore, whenever an MI command results in an error, we recommend
21071 and supplies them to target on each command. This is convenient,
21072 because a command line user would not want to specify that information
21073 explicitly on each command, and because user interacts with GDB via a
21083 operating on a wrong one. Therefore, each MI command should explicitly
21085 each MI command accepts the `--thread' and `--frame' options, the value
21093 another example, if the user issues the CLI `thread' command via the
21102 simplest way is for frontend to emit `-thread-select' command before
21103 every command. This doubles the number of commands that need to be
21118 27.1.2 Asynchronous command execution and non-stop mode
21122 the target is running. This is called "asynchronous command execution"
21124 for asynchronous execution using the `-gdb-set target-async 1' command,
21128 enabled using the `-list-target-features' command.
21130 Even if GDB can accept a command while target is running, many
21132 Therefore, asynchronous command execution is most useful when combined
21176 command, `-list-thread-groups', returns the list of top-level thread
21179 `-list-thread-groups' command, it is possible to obtain the members of
21185 but that can be attached to, using the `-target-attach' command. The
21196 File: gdb.info, Node: GDB/MI Command Syntax, Next: GDB/MI Compatibility with CLI, Prev: GDB/MI General Design, Up: GDB/MI
21198 27.2 GDB/MI Command Syntax
21207 File: gdb.info, Node: GDB/MI Input Syntax, Next: GDB/MI Output Syntax, Up: GDB/MI Command Syntax
21212 `COMMAND ==>'
21213 `CLI-COMMAND | MI-COMMAND'
21215 `CLI-COMMAND ==>'
21216 `[ TOKEN ] CLI-COMMAND NL', where CLI-COMMAND is any existing GDB
21217 CLI command.
21219 `MI-COMMAND ==>'
21250 * The `TOKEN', when present, is passed back when the command
21266 File: gdb.info, Node: GDB/MI Output Syntax, Prev: GDB/MI Input Syntax, Up: GDB/MI Command Syntax
21273 for the most recent command. The sequence of output records is
21276 If an input command was prefixed with a `TOKEN' then the
21277 corresponding output for that command will also be prefixed by that same
21357 should be no need to associate async output to any prior command.
21372 the console. It is the textual response to a CLI command. All
21389 File: gdb.info, Node: GDB/MI Compatibility with CLI, Next: GDB/MI Development and Front Ends, Prev: GDB/MI Command Syntax, Up: GDB/MI
21397 command lists are not executed and some CLI commands, such as `if',
21402 recommended that front ends use the `-interpreter-exec' command (*note
21426 * New fields may be added to the output of any MI command.
21464 GDB/MI command includes one of the following result indications:
21472 output instead of `^done' if the command has resumed the target.
21539 only once for any command. GDB may emit this notification several
21561 An -exec-finish or similar CLI command was accomplished.
21564 An -exec-until or similar CLI command was accomplished.
21571 -exec-step-instruction or similar CLI command was
21628 command. This notification is not emitted as result of
21629 `-thread-select' command but is emitted whenever an MI command
21632 user-defined command), the CLI `thread' command, will generate
21739 File: gdb.info, Node: GDB/MI Simple Examples, Next: GDB/MI Command Description Format, Prev: GDB/MI Output Records, Up: GDB/MI
21800 A Bad Command
21803 Here's what happens if you pass a non-existent command:
21806 <- ^error,msg="Undefined MI command: rubbish"
21810 File: gdb.info, Node: GDB/MI Command Description Format, Next: GDB/MI Breakpoint Commands, Prev: GDB/MI Simple Examples, Up: GDB/MI
21812 27.7 GDB/MI Command Description Format
21831 For each command in the block, the following is described:
21836 -command ARGS...
21841 GDB Command
21844 The corresponding GDB CLI command(s), if any.
21854 File: gdb.info, Node: GDB/MI Breakpoint Commands, Next: GDB/MI Program Context, Prev: GDB/MI Command Description Format, Up: GDB/MI
21861 The `-break-after' Command
21871 `-break-list' command, see the description of the `-break-list' command
21874 GDB Command
21877 The corresponding GDB command is `ignore'.
21905 The `-break-commands' Command
21915 If no command is specified, any previously-set commands are cleared.
21920 GDB Command
21923 The corresponding GDB command is `commands'.
21938 The `-break-condition' Command
21948 (see the description of the `-break-list' command below).
21950 GDB Command
21953 The corresponding GDB command is `condition'.
21975 The `-break-delete' Command
21986 GDB Command
21989 The corresponding GDB command is `delete'.
22009 The `-break-disable' Command
22020 GDB Command
22023 The corresponding GDB command is `disable'.
22045 The `-break-enable' Command
22055 GDB Command
22058 The corresponding GDB command is `enable'.
22080 The `-break-info' Command
22090 GDB Command
22093 The corresponding GDB command is `info break BREAKPOINT'.
22100 The `-break-insert' Command
22120 The possible optional parameters of this command are:
22166 GDB Command
22205 The `-break-list' Command
22242 GDB Command
22245 The corresponding GDB command is `info break'.
22280 The `-break-passcount' Command
22290 error is emitted. This corresponds to CLI command `passcount'.
22292 The `-break-watch' Command
22312 GDB Command
22438 The `-exec-arguments' Command
22449 GDB Command
22452 The corresponding GDB command is `set args'.
22462 The `-environment-cd' Command
22472 GDB Command
22475 The corresponding GDB command is `cd'.
22485 The `-environment-directory' Command
22498 Specifying multiple directories in a single command results in the
22500 they were presented in the command. If blanks are needed as part of a
22502 command output, the path will show up separated by the system
22507 GDB Command
22510 The corresponding GDB command is `dir'.
22529 The `-environment-path' Command
22543 single command results in the directories added to the beginning of the
22544 search path in the same order they were presented in the command. If
22546 used around the name. In the command output, the path will show up
22551 GDB Command
22554 The corresponding GDB command is `path'.
22570 The `-environment-pwd' Command
22580 GDB Command
22583 The corresponding GDB command is `pwd'.
22599 The `-thread-info' Command
22611 GDB Command
22614 The `info thread' command prints the same information about all threads.
22638 `thread name' command, then this name is given. Otherwise, if GDB
22680 The `-thread-list-ids' Command
22691 This command is retained for historical reasons, the `-thread-info'
22692 command should be used instead.
22694 GDB Command
22708 The `-thread-select' Command
22719 This command is deprecated in favor of explicitly using the
22720 `--thread' option to each command.
22722 GDB Command
22725 The corresponding GDB command is `thread'.
22759 The `-exec-continue' Command
22785 GDB Command
22802 The `-exec-finish' Command
22815 GDB Command
22818 The corresponding GDB command is `finish'.
22845 The `-exec-interrupt' Command
22855 command that has been interrupted. The token for the interrupt itself
22859 Note that when asynchronous execution is enabled, this command is
22869 GDB Command
22872 The corresponding GDB command is `interrupt'.
22895 The `-exec-jump' Command
22907 GDB Command
22910 The corresponding GDB command is `jump'.
22919 The `-exec-next' Command
22932 line. If you issue this command on the first line of a function, it
22936 GDB Command
22939 The corresponding GDB command is `next'.
22950 The `-exec-next-instruction' Command
22969 GDB Command
22972 The corresponding GDB command is `nexti'.
22986 The `-exec-return' Command
22997 GDB Command
23000 The corresponding GDB command is `return'.
23029 The `-exec-run' Command
23047 GDB Command
23050 The corresponding GDB command is `run'.
23094 The `-exec-step' Command
23109 GDB Command
23112 The corresponding GDB command is `step'.
23136 The `-exec-step-instruction' Command
23151 GDB Command
23154 The corresponding GDB command is `stepi'.
23177 The `-exec-until' Command
23190 GDB Command
23193 The corresponding GDB command is `until'.
23213 The `-stack-info-frame' Command
23223 GDB Command
23226 The corresponding GDB command is `info frame' or `frame' (without
23239 The `-stack-info-depth' Command
23250 GDB Command
23253 There's no equivalent GDB command.
23277 The `-stack-list-arguments' Command
23300 Use of this command to obtain arguments in a single frame is
23301 deprecated in favor of the `-stack-list-variables' command.
23303 GDB Command
23306 GDB does not have an equivalent command. `gdbtk' has a `gdb_get_args'
23307 command which partially overlaps with the functionality of
23366 The `-stack-list-frames' Command
23400 If invoked without arguments, this command prints a backtrace for the
23408 GDB Command
23469 The `-stack-list-locals' Command
23486 This command is deprecated in favor of the `-stack-list-variables'
23487 command.
23489 GDB Command
23509 The `-stack-list-variables' Command
23532 The `-stack-select-frame' Command
23543 This command in deprecated in favor of passing the `--frame' option
23544 to every command.
23546 GDB Command
23597 each time the program stops. Instead, MI provides an update command
23673 The `-enable-pretty-printing' Command
23686 command will still succeed (and do nothing).
23691 The `-var-create' Command
23707 provided that one does not specify NAME of that format. The command
23727 cases. If the `-enable-pretty-printing' command is not sent, then GDB
23777 The `-var-delete' Command
23790 The `-var-set-format' Command
23813 The `-var-show-format' Command
23826 The `-var-info-num-children' Command
23842 The `-var-list-children' Command
23935 The `-var-info-type' Command
23948 The `-var-info-expression' Command
23968 Note that the output of the `-var-list-children' command also
23969 includes those expressions, so the `-var-info-expression' command is of
23972 The `-var-info-path-expression' Command
23982 with the `-var-info-expression' command, which result can be used only
23984 command is creating a watchpoint from a variable object.
23986 This command is currently not valid for children of a dynamic varobj,
23996 The `-var-show-attributes' Command
24010 The `-var-evaluate-expression' Command
24024 using the `-var-set-format' command.
24031 The `-var-assign' Command
24055 The `-var-update' Command
24109 command. The front end should normally choose to delete
24169 The `-var-set-frozen' Command
24195 The `-var-set-update-range' command
24218 The `-var-set-visualizer' command
24245 command `-list-features' (*note GDB/MI Miscellaneous Commands::) can be
24279 The `-data-disassemble' Command
24335 GDB Command
24338 There's no direct mapping from this command to the CLI.
24408 The `-data-evaluate-expression' Command
24420 GDB Command
24424 `gdbtk' only, there's a corresponding `gdb_eval' command.
24430 "tokens" described in *note GDB/MI Command Syntax: GDB/MI Command
24446 The `-data-list-changed-registers' Command
24456 GDB Command
24459 GDB doesn't have a direct analog for this command; `gdbtk' has the
24460 corresponding command `gdb_changed_register_list'.
24482 The `-data-list-register-names' Command
24497 GDB Command
24500 GDB does not have a command which corresponds to
24502 command `gdb_regnames'.
24522 The `-data-list-register-values' Command
24556 GDB Command
24612 The `-data-read-memory' Command
24615 This command is deprecated, use `-data-read-memory-bytes' instead.
24633 the same as for GDB's `print' command (*note Output Formats:
24655 This command displays memory contents as a table of NR-ROWS by
24666 GDB Command
24669 The corresponding GDB command is `x'. `gdbtk' has `gdb_get_mem' memory
24670 read command.
24719 The `-data-read-memory-bytes' Command
24745 This command attempts to read all accessible memory regions in the
24761 the command includes a field named `memory' whose content is a list of
24779 GDB Command
24782 The corresponding GDB command is `x'.
24794 The `-data-write-memory-bytes' Command
24813 GDB Command
24816 There's no corresponding GDB command.
24835 The `-trace-find' Command
24901 GDB Command
24904 The corresponding GDB command is `tfind'.
24918 GDB Command
24921 The corresponding GDB command is `tvariable'.
24948 GDB Command
24951 The corresponding GDB command is `tvariables'.
24978 GDB Command
24981 The corresponding GDB command is `tsave'.
24991 Starts a tracing experiments. The result of this command does not
24994 GDB Command
24997 The corresponding GDB command is `tstart'.
25026 the `-trace-stop' command. The value of `overflow' means the
25062 GDB Command
25065 The corresponding GDB command is `tstatus'.
25075 Stops a tracing experiment. The result of this command has the same
25079 GDB Command
25082 The corresponding GDB command is `tstop'.
25090 The `-symbol-list-lines' Command
25102 GDB Command
25105 There is no corresponding GDB command.
25124 The `-file-exec-and-symbols' Command
25134 command clears the executable and symbol information. If breakpoints
25135 are set when using this command with no arguments, GDB will produce
25139 GDB Command
25142 The corresponding GDB command is `file'.
25152 The `-file-exec-file' Command
25166 GDB Command
25169 The corresponding GDB command is `exec-file'.
25179 The `-file-list-exec-source-file' Command
25192 GDB Command
25205 The `-file-list-exec-source-files' Command
25218 GDB Command
25221 The GDB equivalent is `info sources'. `gdbtk' has an analogous command
25235 The `-file-symbol-file' Command
25247 GDB Command
25250 The corresponding GDB command is `symbol-file'.
25266 The `-target-attach' Command
25278 GDB Command
25281 The corresponding GDB command is `attach'.
25293 The `-target-detach' Command
25305 GDB Command
25308 The corresponding GDB command is `detach'.
25318 The `-target-disconnect' Command
25329 GDB Command
25332 The corresponding GDB command is `disconnect'.
25342 The `-target-download' Command
25386 GDB Command
25389 The corresponding GDB command is `load'.
25445 GDB Command
25455 The `-target-select' Command
25463 Connect GDB to the remote target. This command takes two args:
25478 GDB Command
25481 The corresponding GDB command is `target'.
25497 The `-target-file-put' Command
25508 GDB Command
25511 The corresponding GDB command is `remote put'.
25521 The `-target-file-get' Command
25532 GDB Command
25535 command is `remote get'.
25545 The `-target-file-delete' Command
25555 GDB Command
25558 The corresponding GDB command is `remote delete'.
25574 The `-gdb-exit' Command
25584 GDB Command
25596 The `-gdb-set' Command
25606 GDB Command
25609 The corresponding GDB command is `set'.
25619 The `-gdb-show' Command
25629 GDB Command
25632 The corresponding GDB command is `show'.
25642 The `-gdb-version' Command
25652 GDB Command
25676 The `-list-features' Command
25680 version of gdb implements. A feature can be a command, or a new field
25681 in an output of some command, or even an important bugfix. While a
25685 The command returns a list of strings, with each string naming an
25698 Indicates presence of the `-var-set-frozen' command, as well as
25704 command.
25712 Indicates presence of the `-thread-info' command.
25719 The `-list-target-features' Command
25724 features reported by the `-list-features' command, the features depend
25736 Indicates that the target is capable of asynchronous command
25745 The `-list-thread-groups' Command
25763 The output of this command may have either a `threads' result or a
25853 The `-add-inferior' Command
25863 be established with the `-file-exec-and-symbols' command (*note GDB/MI
25864 File Commands::). The command response has a single field,
25875 The `-interpreter-exec' Command
25881 -interpreter-exec INTERPRETER COMMAND
25882 Execute the specified COMMAND in the given INTERPRETER.
25884 GDB Command
25887 The corresponding GDB command is `interpreter-exec'.
25900 The `-inferior-tty-set' Command
25910 GDB Command
25913 The corresponding GDB command is `set inferior-tty' /dev/pts/1.
25923 The `-inferior-tty-show' Command
25933 GDB Command
25936 The corresponding GDB command is `show inferior-tty'.
25949 The `-enable-timings' Command
25958 command as a field in its output. This command is to help frontend
25962 GDB Command
26008 * Server Prefix:: Issuing a command without affecting user state.
26037 command line option (*note Mode Options::), controls how much
26046 The GDB command `set annotate' sets the level of annotations to
26085 If you prefix a command with `server ' then it will not affect the
26086 command history, nor will it affect GDB's notion of which command to
26093 history, use the `output' command instead of the `print' command.
26105 know when to send output, when the output from a given command is over,
26123 When GDB is prompting for a command (the main GDB prompt).
26127 command. The annotations are repeated for each command which is
26185 The frames (for example, output from the `backtrace' command) may
26198 When the program starts executing due to a GDB command such as `step'
26399 File: gdb.info, Node: GDB Bugs, Next: Command Line Editing, Prev: JIT Interface, Up: Top
26518 * The command arguments you gave the compiler to compile your
26610 File: gdb.info, Node: Command Line Editing, Next: Using History Interactively, Prev: GDB Bugs, Up: Top
26612 31 Command Line Editing
26615 This chapter describes the basic features of the GNU command line
26629 File: gdb.info, Node: Introduction and Notation, Next: Readline Interaction, Up: Command Line Editing
26665 File: gdb.info, Node: Readline Interaction, Next: Readline Init File, Prev: Introduction and Notation, Up: Command Line Editing
26729 Undo the last editing command. You can undo all the way back to an
26779 If the description for a command says that it `kills' text, then you
26783 When you use a kill command, the text is saved in a "kill-ring".
26819 if the prior command is `C-y' or `M-y'.
26830 command which normally acts in a forward direction, that command will
26834 The general way to pass numeric arguments to a command is to type
26835 meta digits before the command. If the first `digit' typed is a minus
26838 remainder of the digits, and then the command. For example, to give
26839 the `C-d' command an argument of 10, you could type `M-1 0 C-d', which
26848 Readline provides commands for searching through the command history
26869 Any other key sequence bound to a Readline command will terminate the
26870 search and execute that command. For instance, a <RET> will terminate
26871 the search and accept the line, thereby executing the command from the
26872 history list. A movement command will terminate the search, make the
26884 File: gdb.info, Node: Readline Init File, Next: Bindable Readline Commands, Prev: Readline Interaction, Up: Command Line Editing
26900 In addition, the `C-x C-r' command re-reads this init file, thus
26925 values of variables in Readline using the `set' command within the
26959 `insert-comment' command is executed. The default value is
27025 command (*note Searching::). If this variable has not been
27033 `vi-command', and `vi-insert'. `vi' is equivalent to
27034 `vi-command'; `emacs' is equivalent to `emacs-standard'. The
27097 simple. First you need to find the name of the command that you
27099 command name, the default keybinding, if any, and a short
27100 description of what the command does.
27102 Once you know the name of the command, simply place on a line in
27103 the init file the name of the key you wish to bind the command to,
27104 a colon, and then the name of the command. The name of the key
27108 In addition to command names, readline allows keys to be bound to
27232 used in conjunction with the `set keymap' command, for
27251 instance, the following command adds a key sequence that
27259 This command, as seen in the previous example, terminates an `$if'
27260 command.
27383 File: gdb.info, Node: Bindable Readline Commands, Next: Readline vi Mode, Prev: Readline Init File, Up: Command Line Editing
27400 sequences. Command names without an accompanying key sequence are
27405 `set-mark' command. The text between the point and mark is referred to
27456 command.
27459 Move `forward' through the history list, fetching the next command.
27490 non-incremental search. By default, this command is unbound.
27495 non-incremental search. By default, this command is unbound.
27498 Insert the first argument to the previous command (usually the
27500 insert the Nth word from the previous command (the words in the
27501 previous command begin with word 0). A negative argument inserts
27502 the Nth word from the end of the previous command. Once the
27507 Insert last argument to the previous command (the last word of the
27571 argument, switches to insert mode. This command affects only
27580 By default, this command is unbound.
27625 Kill the text in the current region. By default, this command is
27630 right away. By default, this command is unbound.
27635 command is unbound.
27640 command is unbound.
27647 if the prior command is `yank' or `yank-pop'.
27660 This is another way to specify an argument. If this command is
27662 sign, those digits define the argument. If the command is
27665 this command is immediately followed by a character that is
27667 command is multiplied by four. The argument count is initially
27699 command is intended to be bound to <TAB>, but is unbound by
27705 behaves identically to `possible-completions'. This command is
27738 Abort the current editing command and ring the terminal's bell
27742 If the metafied character X is lowercase, run the command that is
27754 `undo' command enough times to get back to the beginning.
27781 numeric argument is supplied, this command acts as a toggle: if
27792 file. This command is unbound by default.
27798 INPUTRC file. This command is unbound by default.
27804 INPUTRC file. This command
27807 When in `vi' command mode, this causes a switch to `emacs' editing
27816 File: gdb.info, Node: Readline vi Mode, Prev: Bindable Readline Commands, Up: Command Line Editing
27827 modes, use the command `M-C-j' (bound to emacs-editing-mode when in
27833 you into `command' mode, where you can edit the text of the line with
27838 File: gdb.info, Node: Using History Interactively, Next: In Memoriam, Prev: Command Line Editing, Up: Top
27864 to a previous command into the current input line, or fix errors in
27890 An event designator is a reference to a command line entry in the
27898 Refer to command line N.
27901 Refer to the command N lines back.
27904 Refer to the previous command. This is a synonym for `!-1'.
27907 Refer to the most recent command starting with STRING.
27910 Refer to the most recent command containing STRING. The trailing
27915 Quick Substitution. Repeat the last command, replacing STRING1
27919 The entire command line typed so far.
27938 designates the preceding command. When you type this, the
27939 preceding command is repeated in toto.
27942 designates the last argument of the preceding command. This may be
27946 designates the second argument of the most recent command starting
27952 The `0'th word. For many applications, this is the command word.
27982 previous command is used as the event.
28007 Print the new command but do not execute it.
28107 installed, chances are it has such a program. The precise command to
28109 devices) is `dvips'. The DVI print command may require a file name
28257 source for the GNU command-line interface
28531 command is useful for debugging the Agent Expression mechanism
28562 Temporary internal breakpoint used by the GDB `until' command.
28566 command.
28606 `maint deprecate COMMAND [REPLACEMENT]'
28607 `maint undeprecate COMMAND'
28608 Deprecate or undeprecate the named COMMAND. Deprecated commands
28610 argument REPLACEMENT says which newer command should be used in
28661 this command sends the string TEXT to the inferior, and displays
28698 The command `maint print raw-registers' includes the contents of
28699 the raw register cache; the command `maint print cooked-registers'
28702 command `maint print register-groups' includes the groups that each
28725 This command forces GDB to flush its internal register cache.
28729 command prints its name, address in memory, and all of its psymtabs
28735 object files matching REGEXP. For each script, this command
28740 This command prints, for each object file in the program, various
28760 This command prints a short description of each layer that was
28768 command is a recursive definition of the data type as stored in
28812 command to enable it. When you enable profiling, the system will
28835 thread-information-block' command.
28838 Control whether to display memory usage for each command. If set
28839 to a nonzero value, GDB will display how much memory each command
28840 took, following the command's own output. This can also be
28841 requested by invoking GDB with the `--statistics' command-line
28845 Control whether to display the execution time for each command. If
28847 execute each command, following the command's own output. The
28852 GDB with the `--statistics' command-line switch (*note Mode
28860 address' command (*note Symbols::), except that this command also
28869 The following command is useful for non-interactive invocations of
28875 and the command is aborted.
29002 For any COMMAND not supported by the stub, an empty response
29092 are problems if the command or the acknowledgment packet is
29141 via the `detach' command.
29408 command in the `vCont' packet.
29483 Run the program FILENAME, passing it each ARGUMENT on its command
29982 non-stop' command; *note Non-Stop Mode::.
30007 command (*note set remote pass-signals: Remote Configuration.).
30012 `qRcmd,COMMAND'
30013 COMMAND (hex encoded) is passed to the local interpreter for
30022 A command response with no output.
30025 A command response with the hex encoded output string OUTPUT.
30033 (Note that the `qRcmd' packet's name is separated from the command
30372 the command by a `,', not a `:', contrary to the naming
30589 `quit' command.
30771 the conditional, and `cmd' for an action command. GDB sends a
30772 separate packet for each command in the action list, in the same
30883 The trace was stopped by a user-originated stop command.
31343 the `set remote noack-packet off' command (*note Remote
31349 Note that `set remote noack-packet' command only affects negotiation
32095 int system(const char *command);
32104 status of the command otherwise. Only the exit status of the
32105 command is returned, which is extracted from the host's `system'
32119 consists entirely of the exit status of the called command.
32123 system-call-allowed 1' command.
32659 those locations are reached. Later, using the `tfind' command, she can
33364 `set architecture' command can be error-prone.
33939 <column name="command">/sbin/init</column>
33946 `command' columns are optional, and will be displayed by GDB. The
35218 * # (a comment): Command Syntax. (line 38)
35254 * --command: File Options. (line 51)
35260 * --eval-command: File Options. (line 57)
35535 * __init__ on Command: Commands In Python. (line 12)
35541 * _NSPrintForDebugger, and printing Objective-C objects: The Print Command with Objective-C.
35544 * abbreviation: Command Syntax. (line 13)
35598 * apply command to several threads: Threads. (line 122)
35824 * command editing: Readline Bare Essentials.
35826 * command files: Command Files. (line 6)
35827 * command history: Command History. (line 6)
35828 * command hooks: Hooks. (line 6)
35829 * command interpreters: Interpreters. (line 6)
35830 * command line editing: Editing. (line 6)
35831 * command scripts, debugging: Messages/Warnings. (line 67)
35832 * command tracing: Messages/Warnings. (line 62)
35852 * comment: Command Syntax. (line 38)
35866 * complete on Command: Commands In Python. (line 73)
35935 * Ctrl-o (operate-and-get-next): Command Syntax. (line 42)
36055 * display command history: Command History. (line 78)
36074 * don't repeat command: Define. (line 61)
36075 * don't repeat Python command: Commands In Python. (line 43)
36077 * dont_repeat on Command: Commands In Python. (line 44)
36117 * editing command lines: Readline Bare Essentials.
36124 * else: Command Files. (line 75)
36144 * end (if/else/while commands): Command Files. (line 104)
36176 * execute commands from a file: Command Files. (line 17)
36178 * execute remote command, remote request: General Query Packets.
36278 * frame, command: Frames. (line 45)
36499 * GDBHISTFILE, environment variable: Command History. (line 26)
36545 * history expansion, turn on/off: Command History. (line 53)
36546 * history file: Command History. (line 26)
36549 * history size: Command History. (line 45)
36550 * history substitution: Command History. (line 26)
36557 * HISTSIZE, environment variable: Command History. (line 45)
36563 * hooks, post-command: Hooks. (line 11)
36564 * hooks, pre-command: Hooks. (line 6)
36581 * if: Command Files. (line 75)
36734 * invoke on Command: Commands In Python. (line 50)
36848 * loop_break: Command Files. (line 94)
36849 * loop_continue: Command Files. (line 98)
37112 * Objective-C, print objects: The Print Command with Objective-C.
37238 * po (print-object): The Print Command with Objective-C.
37278 * print an Objective-C object description: The Print Command with Objective-C.
37290 * print-object: The Print Command with Objective-C.
37530 * repeating command sequences: Command Syntax. (line 42)
37531 * repeating commands: Command Syntax. (line 21)
37549 * RET (repeat last command): Command Syntax. (line 21)
37593 * save command history: Command History. (line 36)
37601 * scripting commands: Command Files. (line 6)
37606 * sds, a command: PowerPC Embedded. (line 91)
37629 * send command to remote monitor: Connecting. (line 105)
37630 * send command to simulator: Embedded Processors. (line 9)
37633 * send PMON command: MIPS Embedded. (line 132)
37643 * server, command prefix: Command History. (line 20)
37714 * set exceptions, Hurd command: Hurd Native. (line 40)
37726 * set history expansion: Command History. (line 65)
37727 * set history filename: Command History. (line 26)
37728 * set history save: Command History. (line 36)
37729 * set history size: Command History. (line 45)
37799 * set signals, Hurd command: Hurd Native. (line 11)
37800 * set sigs, Hurd command: Hurd Native. (line 11)
37811 * set stopped, Hurd command: Hurd Native. (line 32)
37827 * set thread, Hurd command: Hurd Native. (line 91)
37892 * show commands: Command History. (line 78)
37923 * show exceptions, Hurd command: Hurd Native. (line 46)
37929 * show history: Command History. (line 70)
37935 * show last commands: Command History. (line 78)
37996 * show signals, Hurd command: Hurd Native. (line 17)
37997 * show sigs, Hurd command: Hurd Native. (line 17)
38003 * show stopped, Hurd command: Hurd Native. (line 37)
38019 * show thread, Hurd command: Hurd Native. (line 101)
38058 * sim, a command: Embedded Processors. (line 13)
38066 * source: Command Files. (line 17)
38130 * stop, a pseudo-command: Hooks. (line 21)
38312 * time of command execution: Maintenance Commands.
38463 * user-defined command: Define. (line 6)
38518 * while: Command Files. (line 86)
38544 * x command, default address: Machine Code. (line 30)
38596 Node: Command Syntax46262
38733 Node: The Print Command with Objective-C440036
38845 Node: Command History677920
38857 Node: Command Files706348
38903 Node: GDB/MI Command Syntax851185
38916 Node: GDB/MI Command Description Format872545
38952 Node: Command Line Editing1018555
