Lines Matching full:note
113 information, see *Note Supported languages: Supported languages. For
114 more information, see *Note C and C++: C.
117 *Note Modula-2: Modula-2.
685 command-line arguments (*note Arguments::) to `-O2 -c foo.c'.
767 Execute GDB commands from file FILE. *Note Command files: Command
805 command options and arguments have been processed. *Note Command
839 Note that targets that give their output via GDB, as opposed to
894 identical to using `set annotate LEVEL' (*note Annotations::).
903 (*note GDB/MI::).
926 source, assembly, registers and GDB command outputs (*note GDB
929 use this option if you run GDB from Emacs (*note Using GDB under
935 which communicate with GDB using it as a back end. *Note Command
939 "GDB/MI interface" (*note The GDB/MI Interface: GDB/MI.) included
946 This is equivalent to the `set write on' command inside GDB (*note
967 (*note interpreter: Mode Options.).
981 5. Reads command files specified by the `-x' option. *Note Command
984 6. Reads the command history recorded in the "history file". *Note
988 Init files use the same syntax as "command files" (*note Command
992 Init files are not executed if you use the `-nx' option (*note Choosing
1041 you can release it with the `detach' command (*note Debugging an
1141 User-defined commands can disable this feature; see *Note dont-repeat:
1149 in a way similar to the common utility `more' (*note Screen size:
1155 nothing. This is useful mainly in command files (*note Command files:
1254 For more information about overloaded functions, see *Note C++
1256 overload-resolution off' to disable overload resolution; see *Note GDB
1357 *Note Index::.
1472 it to us as a bug (including a test case!). *Note Variables::, for
1480 (*note Macros::). Most compilers do not include information about
1500 argument to GDB (*note Getting In and Out of GDB: Invocation.), or
1501 by using the `file' or `exec-file' command (*note Commands to
1523 which shell is used with the `SHELL' environment variable. *Note
1530 *Note Your program's environment: Environment.
1534 the GDB working directory with the `cd' command in GDB. *Note
1541 a different device for your program. *Note Your program's input
1550 immediately. *Note Stopping and continuing: Stopping, for discussion
1553 `call' commands. *Note Examining Data: Data.
1582 underlying `run' command. Note that the same arguments will be
1706 that specify files for GDB to operate on. *Note Commands to specify
1718 the `/proc' support, you can use the `info proc' command (*note SVR4
1799 program is not found) by using the source file search path (*note
1801 `file' command to load the program. *Note Commands to Specify Files:
1824 you need to confirm by using the `set confirm' command (*note Optional
2009 *Note Stopping and starting multi-thread programs: Thread Stops, for
2013 *Note Setting watchpoints: Set Watchpoints, for information about
2036 debugging the parent process) to attach to the child process (*note
2134 `vfork', or `exec' call is made. *Note Setting catchpoints: Set
2188 Note that breakpoints, GDB variables, command history etc. are
2281 breakpoints with the `break' command and its variants (*note Setting
2297 (*note Setting watchpoints: Set Watchpoints.), but aside from that, you
2302 automatically whenever GDB stops at a breakpoint. *Note Automatic
2308 different command to set a catchpoint (*note Setting catchpoints: Set
2311 `handle' command; see *Note Signals: Signals.)
2347 breakpoint you've set most recently; see *Note Convenience variables:
2357 *Note Breakpoint menus: Breakpoint Menus, for a discussion of that
2364 "stack frame". (*Note Frames: Frames, for a description of stack
2390 (*note Examining the Stack: Stack.). In any selected frame but the
2410 specifying where to break. *Note Break conditions: Conditions,
2417 time your program stops there. *Note Disabling breakpoints:
2434 unused hardware breakpoints before setting new ones (*note
2435 Disabling: Disabling.). *Note Break conditions: Conditions. For
2437 breakpoints GDB will use, see *Note set remote
2447 not have this support. *Note Disabling breakpoints: Disabling.
2448 See also *Note Break conditions: Conditions.
2459 tools like `grep'. Note that this is different from the syntax
2519 the last breakpoint listed (*note Examining memory: Memory.).
2531 the breakpoints are conditional, this is even useful (*note Break
2585 (*note maint info breakpoints::).
2607 language (*note Languages::).
2638 catchpoints; it is the same as `info break' (*note Set Breaks::).
2650 system supports them. (Note that hardware-assisted watchpoints that
2661 watchpoints GDB will use, see *Note set remote
2750 *Note set remote hardware-watchpoint-limit::.
2833 takes place, set a breakpoint on `__raise_exception' (*note
2836 With a conditional breakpoint (*note Break conditions: Conditions.)
2865 the selected stack frame (*note Selecting a frame: Selection.).
2941 Except for a breakpoint set with `tbreak' (*note Setting
2946 breakpoints; see *Note Continuing and stepping: Continuing and
2958 (*note Expressions: Expressions.). A breakpoint with a condition
2980 without checking the condition of this one.) Note that breakpoint
2983 (*note Breakpoint command lists: Break Commands.).
2986 `if' in the arguments to the `break' command. *Note Setting
3008 condition, like `break if ...') is given, however. *Note
3037 argument to `continue', rather than using `ignore'. *Note
3046 is decremented each time. *Note Convenience variables:
3098 breakpoints. *Note Commands for controlled output: Output.
3270 to resume execution. *Note Signals: Signals.)
3279 effect is like that of `ignore' (*note Break conditions:
3292 (*note Returning from a function: Returning.) to go back to the calling
3293 function; or `jump' (*note Continuing at a different address: Jumping.)
3296 A typical technique for using stepping is to set a breakpoint (*note
3371 Contrast this with the `return' command (*note Returning from a
3419 the forms of argument acceptable to `break' (*note Setting
3455 instruction to be executed, each time your program stops. *Note
3567 you can continue with `signal 0'. *Note Giving your program a signal:
3576 When your program has multiple threads (*note Debugging programs with
3698 whichever frame you are interested in. *Note Selecting a frame:
3703 command (*note Information about a frame: Frame Info.).
3737 is kept in a register called the "frame pointer register" (*note $fp:
3807 the threads, use the command `thread apply' (*note thread apply:
3898 (1) Note that embedded programs (the so-called "free-standing"
3963 editing program by typing `edit'. *Note Printing source lines: List,
3988 argument, this command is used to select a stack frame. *Note
4023 *Note Selecting a frame: Selection.
4038 `up', `down', or `frame' commands); then type `info catch'. *Note
4052 (*note Selecting a frame: Selection.), GDB prints the line where
4057 use Emacs facilities to view source; see *Note Using GDB under GNU
4091 printed as part of displaying a stack frame (*note Examining the
4286 Note that the executable search path is _not_ used to locate the
4305 and the second specifying how it should be rewritten. In *Note set
4316 path substitution rule, use the `set substitute-path' command (*note
4439 ways understood by the `list' command (*note Printing source
4455 sufficient to begin examining the machine code (*note Examining memory:
4457 variable `$_' (*note Convenience variables: Convenience Vars.).
4512 written in (*note Using GDB with Different Languages: Languages.).
4519 letter specifying the format; see *Note Output formats: Output
4525 "value history"; *note Value history: Value History.). This
4531 specified format. *Note Examining memory: Memory.
4535 rather than `print'. *Note Examining the Symbol Table: Symbols.
4570 compiled your program to include this information; see *Note
4579 examples in this manual are in C. *Note Using GDB with Different
4595 *Note Artificial arrays: Arrays, for more information.
4599 function where it is defined. *Note Program variables: Variables.
4618 (*note Selecting a frame: Selection.); they must be either:
4696 (`-gdwarf-2'), which is also an effective form for debug info. *Note
4698 Options. *Note Debugging C++: C, for more info about debug info formats
4703 information, GDB will say `<incomplete type>'. *Note incomplete type:
4736 (*note Value history: Value History.), after printing one out.
4754 to use a convenience variable (*note Convenience variables: Convenience
4809 The command `info symbol 0x54320' yields similar results. *Note
4822 For example, to print the program counter in hex (*note
4827 Note that no space is required before the slash; this is because command
4837 with the `x' command, where `b' stands for "byte"; see *Note Examining
4894 *Note Expressions: Expressions, for more information on
4904 memory above the stack pointer (here, `$sp'; *note Registers:
4917 machine instructions; see *Note Source and machine code: Machine Code.
4942 (*note Remote::), you may wish to verify the program's image in the
4981 time your program stops. *Note Expressions: Expressions.
4988 display it each time in the specified format FMT. *Note Output
4995 ADDR'. *Note Examining memory: Memory.
4999 common name for the program counter; *note Registers: Registers.).
5413 Note that the history records values, not expressions. If the value
5451 predefined machine-specific register names (*note Registers:
5453 preceded by `$'. *Note Value history: Value History.)
5503 last address examined (*note Examining memory: Memory.). Other
5618 (*note Selecting a frame: Selection.). This means that you get the
5636 *Note Returning from a function: Returning.
5696 support of the `qXfer:auxv:read' packet, see *Note qXfer auxiliary
5733 Note that UPPER == 0 is a special case: it is treated as the the
5899 a core file, unless this feature is disabled by the user. *Note
5914 Note that this command is implemented only for some systems (as of
5931 protocol (*note Remote Debugging: Remote.) to debug a program running
5996 Note that these are all single-byte character sets. More work inside
6121 (*note Remote::). Such caching generally improves performance, because
6157 `-g' flag. *Note Compilation::.
6165 see *Note List::.
6288 In the example above, note that `macro expand-once' expands only the
6365 targets. *Note Targets::. In addition, your remote target must know
6369 to implement tracepoints are described in *Note Tracepoint Packets::.
6386 tracepoints can be set. Like a breakpoint (*note Set Breaks::), a
6419 the target program. *Note Set Breaks::. The `trace' command
6571 The command `info scope' (*note info scope: Symbols.) is
6638 *Note*: a trace experiment and data collection may stop
6639 automatically if any tracepoint's passcount is reached (*note
6861 definitions, use the `source' command (*note Command Files::).
6885 Note: `$trace_file' is not suitable for use in `printf', use
6968 The diagram (*note A code overlay::) shows a system with separate
7006 program; see *Note Overlay Description: (ld.info)Overlay
7083 see which overlays are mapped. For details, see *Note Automatic
7147 auto' command (*note Overlay Commands::), GDB looks in the inferior's
7201 addresses. To do this, you must write a linker script (*note Overlay
7293 associated with a filename extension. *Note Displaying the language:
7351 extension. *Note Displaying the language: Show.
7419 *Note Information about a frame: Frame Info, to identify the other
7423 Display the source language of this source file. *Note Examining
7461 source language. *Note Supported languages: Supported languages, for
7505 operators. *Note Supported languages: Supported languages, for further
7513 *Note Supported languages: Supported languages, for the default
7561 specific to individual compilers or machines. *Note Supported
7570 *Note Supported languages: Supported languages, for the default
7601 the `{type}addr' construct (*note Expressions: Expressions.) can be
7639 command-line options `-gdwarf-2' and `-gstabs+'. *Note Options for
7726 The GDB "artificial array" operator (*note Expressions:
7789 Doubled colons also represent the GDB scope operator (*note
7899 `set overload-resolution off'. *Note GDB features for C++:
7906 The GDB command-completion facility can simplify this; see *Note
7924 reference to source files, in both C and C++ debugging (*note
7946 language to C or C++. *Note Having GDB infer the source language:
7981 with pointers and a memory allocation function. *Note Expressions:
8000 you want. *Note Breakpoint menus: Breakpoint Menus.
8005 of any special classes. *Note Setting breakpoints: Set Breaks.
8009 Debug C++ exception handling using these commands. *Note Setting
8014 type TYPENAME. *Note Examining the Symbol Table: Symbols.
8022 *Note Print settings: Print Settings.
8027 objects. *Note Print settings: Print Settings.
8031 Control the format for printing virtual function tables. *Note
8039 argument types, using the standard C++ conversion rules (see *Note
8060 available choices, or to finish the type list for you. *Note
8070 options that are useful for debugging Objective-C code. See also *Note
8071 info classes: Symbols, and *Note info selectors: Symbols, for a few
8198 the `set case-insensitive' command, see *Note Symbols::, for the
8228 controls whether static members of Pascal objects are displayed. *Note
8316 The GDB "artificial array" operator (*note Expressions:
8500 sequences in the style of C are also allowed. *Note C and C++
8553 Note that at present you cannot interactively manipulate set
8566 Note that the array handling is not yet complete and although the
8654 language to Modula-2. *Note Having GDB set the language automatically:
8697 * They have been declared on the same line. (Note: This is true of
8747 The `@' operator (*note Expressions: Expressions.), while available
8927 Ada (*note Expressions::):
8945 * A name starting with `$' is a convenience variable (*note
8946 Convenience Vars::) or a machine register (*note Registers::).
9029 Besides the omissions listed previously (*note Omissions from Ada::),
9093 (*note Choosing files: File Options.), or by one of the file-management
9094 commands (*note Commands to specify files: Files.).
9099 (*note Program variables: Variables.). File names are recorded in
9132 Note the contrast with `print &SYMBOL', which does not work at all
9156 STRUCT-TAG', `union UNION-TAG' or `enum ENUM-TAG'. *Note
9162 type. *Note Expressions: Expressions.
9229 collect during a "trace experiment", see *Note collect: Tracepoint
9347 which GDB has read some symbols. *Note Commands to specify files:
9428 *Note Expressions: Expressions. For example,
9433 the assignment expression (which is 4). *Note Using GDB with Different
9440 is not put in the value history (*note Value history: Value History.).
9497 (*note Expressions: Expressions.). For example, `{int}0x83040' refers
9517 immediately if there is a breakpoint there. *Note Printing source
9520 with `jump'. *Note Setting breakpoints: Set Breaks.
9545 *Note Continuing and stepping: Continuing and Stepping.
9575 tables (*note Signals::). The `signal' command passes the signal
9595 This pops the selected stack frame (*note Selecting a frame:
9603 returned. In contrast, the `finish' command (*note Continuing and
9704 start-up commands (*note Getting In and Out of GDB: Invocation.).
9708 to use. Or you are debugging a remote target via `gdbserver' (*note
9726 -write' to patch object files using this technique. Note that GDB
9777 these pauses into messages if desired. *Note Optional warnings
9782 symbol table data in full right away. Note that "stabs-in-COFF"
9803 Note that the core file is ignored when your program is actually
9807 `kill' command (*note Killing the child process: Kill Process.).
9872 for the `dll-symbols' command (*note Cygwin Native::). GDB
9890 current target (*note Specifying a Debugging Target: Targets.),
10264 many times the problems occur, with the `set complaints' command (*note
10288 verbose on'. *Note Optional warnings and messages:
10345 target types configured for GDB (*note Commands for managing targets:
10401 file or executable target (*note Commands to specify files: Files.).
10403 `attach' command (*note Debugging an already-running process: Attach.).
10427 (*note Commands to specify files: Files.).
10443 *Note Commands to specify files: Files.
10465 over MEDIUM for debugging. *Note Remote Debugging::.
10487 in *Note Embedded Processors: Embedded Processors.
10568 Note that these commands merely adjust interpretation of symbolic
10637 `--baud' option, or use the `set remotebaud' command (*note set
10659 Note that the colon is still required here.
10804 connect to your target (*note Connecting to a remote target:
10831 extensions of the remote protocol, see *Note system-call-allowed:
10909 information about each packet, see *Note Remote Protocol::.
10975 (*note Specifying a Debugging Target: Targets.).
10983 `gdbserver' instead of linking a stub into your program. *Note
11153 (*note What you must do for the stub: Bootstrapping.):
11182 7. Start GDB on the host, and connect to the target (*note Connecting
11448 Note that you must cast the addresses of variables to a `char *',
11506 subsubsection *note Non-debug DLL symbols:: describes working with DLLs
11600 Note that before the debugged program has started execution, no DLLs
11605 library information in *note Files:: or the `dll-symbols' command in
11606 *note Cygwin Native::. Currently, explicitly loading symbols from a DLL
11624 Note that the internal name of the DLL may be all upper-case, even
11628 even `maint print msymbols' (see *note Symbols::). Here's an example:
11652 the symbol. Also note that the actual contents of the memory contained
11939 path (*note Your program's environment: Environment.); if it fails to
11980 editing and recompiling the corresponding source file. Note that this
12241 *Note Commands to specify files: Files.)
12322 breakpoints. *Note hardware-assisted breakpoint: Set Breaks, for
12809 searching the directories listed in the directory search path (*note
12954 As well as making available all the usual machine registers (*note
13206 *Note set mipsfpu: MIPS Embedded.
13263 command. For commands controlling how GDB displays data, see *Note
13324 *Note Command Line Editing::, for more details about the Readline
13339 provide the history facility. *Note Using History Interactively::, for
13379 *Note Event Designators::, for more details.
13595 `symbol-file' in *Note Commands to specify files: Files.
13608 this information useful (*note Errors reading symbol files: Symbol
13791 Aside from breakpoint commands (*note Breakpoint command lists: Break
13823 arguments. Note the arguments are text substitutions, so they may
13862 command should not be repeated when the user hits <RET> (*note
13882 use control flow commands, described in *Note Command Files::.
14087 history either. *Note Expressions: Expressions, for more
14092 formats as for `print'. *Note Output formats: Output Formats, for
14139 IDE. For more information, see *Note The GDB/MI Interface: GDB/MI.
14271 Indicates the current gdb target (*note Specifying a Debugging
14281 is demangled if demangling is turned on (*note Print Settings::).
14299 The TUI installs several key bindings in the readline keymaps (*note
14339 commands (*note TUI Single Key Mode::).
14595 specify files for GDB to operate on. *Note Commands to specify files:
14632 (*note Numeric Arguments: (Emacs)Arguments.), like the GDB `up'
14663 manual (*note Debuggers: (Emacs)Debuggers.).
14676 (*note Mode Options::). It is specifically intended to support the
14683 Note that GDB/MI is still under construction, so some of the
14684 features described below are incomplete and subject to change (*note
14914 *Note GDB/MI Stream Records: GDB/MI Stream Records, for more details
14931 recommended that front ends use the `-interpreter-exec' command (*note
15023 identifies its stream (*note GDB/MI Output Syntax: GDB/MI Output
15109 Note the the line breaks shown in the examples are here only for
15475 Note: this format is open to change.
15605 will trigger when the memory location is accessed for writing. *Note
15608 Note that `-break-list' will report a single list of watchpoints and
15659 program execution. Note that once the watchpoint goes out of scope, it
16105 Interrupts the background execution of the target. Note how the
16976 Note that one must invoke `-var-list-children' for a variable before
17015 are printed in the manner described for `-var-list-children' (*note
17090 Note that whatever included in the instruction field, is not
17189 "tokens" described in *Note GDB/MI Command Syntax: GDB/MI Command
17323 For a PPC MBX board (note: line breaks are for readability only, they
17389 the same as for GDB's `print' command (*note Output formats:
18041 Each message is sent as status record (*note GDB/MI Output Syntax:
18066 Note: each status message appears on a single line. Here the messages
18211 Device names, host names and the like. *Note Commands for
18447 (*note GDB/MI::).
18480 command line option (*note Mode Options::), controls how much
18485 level 2 annotations have been made obsolete (*note Limitations of the
18563 When GDB is asking the user to press return to continue. Note:
18687 in the form `0x' followed by one or more lowercase hex digits (note
18724 (Note that if you're cross debugging, the problem may also be
18728 is a bug. However, you should note that your idea of "invalid
18951 when seen in this text, or in an init file (*note Readline Init File::).
19212 (*note Conditional Init Constructs::). Other lines denote variable
19317 command (*note Searching::). If this variable has not been
20650 options not listed here. *note (configure.info)What Configure Does::,
20716 reference. (For commands that turn on debugging messages, see *Note
20722 (*note Agent Expressions::).
20839 register is a member of. *Note Registers: (gdbint)Registers.
20930 switch (*note Mode Options::).
20937 command-line switch (*note Mode Options::).
20944 address' command (*note Symbols::), except that this command also
21002 Implementors should note that prior to GDB 5.0 the protocol
21029 Implementors should note
21079 COMMANDs and their corresponding response DATA. *Note File-I/O remote
21092 Note that all packet forms beginning with an upper- or lower-case
21110 Reply: *Note Stop Reply Packets::, for the reply specifications.
21142 Don't use this packet. Use the `Z' and `z' packets instead (*note
21149 Reply: *Note Stop Reply Packets::, for the reply specifications.
21155 Reply: *Note Stop Reply Packets::, for the reply specifications.
21160 Don't use this packet; instead, define a general set packet (*note
21176 part of the File-I/O protocol extension. *Note File-I/O remote
21196 Write general registers. *Note read registers packet::, for a
21226 Signal, then cycle step. *Note step with signal packet::. *Note
21237 Read LENGTH bytes of memory starting at address ADDR. Note that
21270 Read the value of register N; N is in hex. *Note read registers
21299 fully in *Note General Query Packets::.
21316 Reply: *Note Stop Reply Packets::, for the reply specifications.
21323 Reply: *Note Stop Reply Packets::, for the reply specifications.
21368 Reply: *Note Stop Reply Packets::, for the reply specifications.
21385 block size appearing in the memory map (*note Memory map
21401 packet (*note Binary Data::). The memory ranges specified by
21431 (*note Binary Data::).
21466 _Implementation note: It is possible for a target to copy or move
21489 _Implementation note: A hardware breakpoint is not affected by code
21603 GDB. *Note File-I/O remote protocol extension::, for a list of
21613 expected to be continued. *Note File-I/O remote protocol
21685 NOTE: This packet replaces the `qL' query (see below).
21778 packets. _Implementors should note that providing access to a
21794 (Note that the `qRcmd' packet's name is separated from the command
21905 (*note qXfer auxiliary vector read::).
21942 *Note Tracepoint Packets::.
21958 (Note that the `qThreadExtraInfo' packet's name is separated from
21968 *Note Tracepoint Packets::.
21982 Access the target's "auxiliary vector". *Note auxiliary
21983 vector: OS Information. Note ANNEX must be empty.
21987 (*note qSupported::).
21990 Access the target's "memory-map". *Note Memory map format::.
21992 (*note qXfer read::).
21996 (*note qSupported::).
22000 Data DATA (*note Binary Data::) has been read from the
22007 Data DATA (*note Binary Data::) has been read from the target.
22029 the data. `DATA...' is the binary-encoded data (*note Binary
22099 Here we describe the packets GDB uses to implement tracepoints (*note
22140 zero.) Note that MASK may be any number of digits long; it
22153 directs. EXPR is an agent expression, as described in *Note
22255 specified via GDB's `remotebreak' setting (*note set remotebreak::).
22264 Overview section (*note Overview::). When a `0x03' byte is transmitted
22266 represent an interrupt. E.g., an `X' packet (*note X packet::), used
22274 Packets (*note Stop Reply Packets::) to GDB as a result of successfully
22491 If the `Ctrl-C' flag is set in the GDB reply packet (*note The F reply
23003 Note that the `isatty' call is treated as a special case: it returns
23081 *Note Limits::, for corresponding MIN and MAX values (similar to
23150 appropriate section (see *Note Integral datatypes::, for details) so
23163 Valid mode bits are described in *Note Constants::. Any other
23182 Note that due to size differences between the host, target, and
23201 appropriate section (see *Note Integral datatypes::, for details) so
23369 The memory map is obtained using the `qXfer:memory-map:read' (*note
23664 product on the stack. Note that, when one multiplies two N-bit
23738 is bit 0) are set to the value of bit N-1. Note that N may be
23761 Note that ADDR may not be aligned in any particular way; the
23877 * The agent arranges to be notified when a trace point is hit. Note
23879 responsible for collecting the data; see *Note Tracing on
23977 saved), and also note the address of the next higher range of memory,
24041 Note that there is not necessarily any connection between the order
24070 First, note that you don't need different bytecodes for different
