Lines Matching full:expressions
106 * Agent Expressions:: The GDB Agent Expression Mechanism
154 entering expressions, printing values, or similar features using Pascal
929 allow Epoch to display values of expressions in a separate window.
935 together with its prompt, values of expressions, source lines, and
1309 Expressions: C Plus Plus Expressions. You can use the command `set
1341 expressions. Also, it only examines the static type of the expression,
2309 breakpoint conditional expressions, command scripts, and so forth.
2783 place to break. *Note Ambiguous Expressions: Ambiguous
2784 Expressions, for a discussion of that situation.
3255 Watching complex expressions that reference many variables can also
3265 variables, or expressions that involve such variables, when they go out
3636 (*note Expressions: Expressions.). A breakpoint with a condition
3687 Expressions: Expressions.
3737 example, you might want to print the values of certain expressions, or
3756 creates multiple breakpoints (*note Ambiguous Expressions:
3757 Ambiguous Expressions.).
3823 (*note Command Files::). Note that watchpoints with expressions
4625 registers, such as with assignment expressions in `print', or the
4634 memory, such as with assignment expressions in `print'. It
5491 of expressions used in locations to cover the situations that
5966 * Expressions:: Expressions
5967 * Ambiguous Expressions:: Ambiguous Expressions
5990 File: gdb.info, Node: Expressions, Next: Ambiguous Expressions, Up: Data
5992 10.1 Expressions
5998 This includes conditional expressions, function calls, casts, and
6003 GDB supports array constants in expressions input by the user. The
6009 Because C is so widespread, most of the expressions shown in
6011 Languages: Languages, for information on how to use expressions in other
6015 expressions regardless of your programming language.
6040 File: gdb.info, Node: Ambiguous Expressions, Next: Variables, Prev: Expressions, Up: Data
6042 10.2 Ambiguous Expressions
6045 Expressions can sometimes contain some ambiguous elements. For
6113 File: gdb.info, Node: Variables, Next: Arrays, Prev: Ambiguous Expressions, Up: Data
6121 Variables in expressions are understood in the selected stack frame
6168 scope resolution operator in GDB expressions.
6253 subscripting, and are coerced to pointers when used in expressions.
6254 Artificial arrays most often appear in expressions via the value history
6442 *Note Expressions: Expressions, for more information on
6443 expressions. The default for ADDR is usually just after the last
6492 subsequent use in expressions as values of the convenience variables
6494 available for use in expressions in the convenience variable `$_'. The
6533 This display shows item numbers, expressions and their current values.
6541 Add the expression EXPR to the list of expressions to display each
6542 time your program stops. *Note Expressions: Expressions.
6564 Remove items from the list of expressions to display. Specify the
6592 Display the current values of the expressions on the list, just as
6596 Print the list of expressions previously set up to display
6598 the values. This includes disabled expressions, which are marked
6599 as such. It also includes expressions which would not be
7163 history". This allows you to refer to them in other expressions.
7194 Note that the history records values, not expressions. If the value
7338 You can refer to machine register contents, in expressions, as variables
7359 expressions) on most machines--whenever they do not conflict with an
7779 values, or use character and string literals in expressions.
7887 you use in expressions:
7934 literals you use in expressions:
8204 evaluate expressions containing macro invocations, show the result of
8414 expressions to evaluate when those tracepoints are reached. Later,
8415 using the `tfind' command, you can examine the values those expressions
8416 had when the program hit the tracepoints. The expressions may also
8685 programming language (*note Expressions: Expressions.). A tracepoint
8697 into an agent expression (*note Agent Expressions::) suitable for
8729 them in print commands and expressions as if they were convenience
8807 Collect values of the given expressions when the tracepoint is hit.
8809 expressions. In addition to global, static, or local variables,
8847 Evaluate the given expressions when the tracepoint is hit. This
8848 command accepts a comma-separated list of expressions. The results
8871 This variable is a list of expressions to collect at each
8873 prepended to every tracepoint action list. The expressions are
8880 Show the list of expressions that are collected by default at each
9082 * Tracepoint expressions are intended to gather objects (lvalues).
9787 language you use to build expressions is called the "working language".
9807 determine how expressions you type are interpreted, how values are
9887 If you allow GDB to set the language automatically, expressions are
9942 expressions that may involve variables in your program.
9986 expressions entered directly into GDB for evaluation via the `print'
10015 For the expressions you use in GDB commands, you can tell the GDB
10019 these, GDB evaluates expressions like the second example above, but
10026 use, and usually arise from expressions, such as the one described
10074 For expressions you use in GDB commands, you can tell GDB to treat
10128 expressions regardless of the language you use: the GDB `@' and `::'
10129 operators, and the `{type}addr' construct (*note Expressions:
10130 Expressions.) can be used with the constructs of any supported language.
10176 * C Plus Plus Expressions:: C++ expressions
10210 The comma or sequencing operator. Expressions in a
10246 these expressions is 0 for false and non-zero for true.
10250 Defined on scalar types. The value of these expressions is 0 for
10257 The GDB "artificial array" operator (*note Expressions:
10258 Expressions.).
10321 Expressions: Expressions.). Same precedence as `::', above.
10328 File: gdb.info, Node: C Constants, Next: C Plus Plus Expressions, Prev: C Operators, Up: C
10378 File: gdb.info, Node: C Plus Plus Expressions, Next: C Defaults, Prev: C Constants, Up: C
10380 15.4.1.3 C++ Expressions
10383 GDB expression handling can interpret most C++ expressions.
10395 1. Member function calls are allowed; you can use expressions like
10400 your expressions have the same namespace available as the member
10429 them in expressions just as you do in C++ source--they are
10439 expressions can use it just as expressions in your program do.
10452 File: gdb.info, Node: C Defaults, Next: C Checks, Prev: C Plus Plus Expressions, Up: C
10474 By default, when GDB parses C or C++ expressions, type checking is not
10500 with pointers and a memory allocation function. *Note Expressions:
10501 Expressions.
10516 *Note Ambiguous Expressions: Ambiguous Expressions.
10519 Setting breakpoints using regular expressions is helpful for
10556 C++ Expressions: C Plus Plus Expressions, for details). If it
10717 * OpenCL C Expressions::
10721 File: gdb.info, Node: OpenCL C Datatypes, Next: OpenCL C Expressions, Up: OpenCL C
10732 File: gdb.info, Node: OpenCL C Expressions, Next: OpenCL C Operators, Prev: OpenCL C Datatypes, Up: OpenCL C
10734 15.4.4.2 OpenCL C Expressions
10739 expressions supported by GDB can be used as well.
10742 File: gdb.info, Node: OpenCL C Operators, Prev: OpenCL C Expressions, Up: OpenCL C
10767 * Fortran Operators:: Fortran operators and expressions
10774 15.4.5.1 Fortran Operators and Expressions
10829 entering expressions, printing values, or similar features using Pascal
10921 The GDB "artificial array" operator (*note Expressions:
10922 Expressions.).
10964 _Warning:_ Set expressions and their operations are not yet
11162 expressions using the debugger.
11354 The `@' operator (*note Expressions: Expressions.), while available
11544 Ada (*note Expressions::):
11608 * You may abbreviate attributes in expressions with any unique,
12021 Expressions: Expressions.
12026 type. *Note Expressions: Expressions.
12233 The output includes expressions which you can copy into a GDB
12307 *Note Expressions: Expressions. For example,
12376 (*note Expressions: Expressions.). For example, `{int}0x83040' refers
12696 some breakpoints and auto-display expressions. This is because
16091 region using one of the following commands (*note Expressions::):
16348 You can refer to these values in GDB expressions with the usual
17387 reference variables, use complex expressions, or even perform inferior
17676 history either. *Note Expressions: Expressions, for more
17677 information on expressions.
17684 `printf TEMPLATE, EXPRESSIONS...'
17685 Print the values of one or more EXPRESSIONS under the control of
17686 the string TEMPLATE. To print several values, make EXPRESSIONS be
17687 a comma-separated list of individual expressions, which may be
17692 printf (TEMPLATE, EXPRESSIONS...);
17696 character cause subsequent EXPRESSIONS to be evaluated, their
17755 `eval TEMPLATE, EXPRESSIONS...'
17756 Convert the values of one or more EXPRESSIONS under the control of
18113 Python expressions that are valid for the value's data type. Here's an
20347 regular expressions. *Note Writing a Pretty-Printer::, for an
20927 expressions.
23570 changing values of expressions. Unlike some other MI interfaces that
23571 work with expressions, variable objects are specifically designed for
23617 the values of variables whose names appear in the expressions are
23969 includes those expressions, so the `-var-info-expression' command is of
24063 Reevaluate the expressions corresponding to the variable object NAME
24277 examine memory and registers, evaluate expressions, etc.
24628 read. Complex expressions containing embedded white space should
24732 read. Complex expressions containing embedded white space should
24806 read. Complex expressions containing embedded white space should
26038 information GDB prints together with its prompt, values of expressions,
28532 (*note Agent Expressions::). The `agent' version produces an
28790 For more information on these expressions, see the DWARF standard
28881 File: gdb.info, Node: Remote Protocol, Next: Agent Expressions, Prev: Maintenance Commands, Up: Top
30289 expressions defined for tracepoints (*note Tracepoint
30732 Agent Expressions::. Each byte of the expression is encoded
30794 expressions.
32645 File: gdb.info, Node: Agent Expressions, Next: Target Descriptions, Prev: Remote Protocol, Up: Top
32658 locations in the program, and arbitrary expressions to evaluate when
32660 examine the values those expressions had when the program hit the trace
32661 points. The expressions may also denote objects in memory --
32670 on the target computes the values of the expressions itself. To avoid
32672 expressions in the source language into a simpler bytecode language, and
32693 * Using Agent Expressions:: How agent expressions fit into the big picture.
32698 File: gdb.info, Node: General Bytecode Design, Next: Bytecode Descriptions, Up: Agent Expressions
32703 The agent represents bytecode expressions as an array of bytes. Each
32746 expressions are only used for unobtrusive debugging, not for patching
32768 in some helpful way. In general, code using agent expressions should
32772 Even complicated C expressions compile to a few bytecode
32820 File: gdb.info, Node: Bytecode Descriptions, Next: Using Agent Expressions, Prev: General Bytecode Design, Up: Agent Expressions
33107 File: gdb.info, Node: Using Agent Expressions, Next: Varying Target Capabilities, Prev: Bytecode Descriptions, Up: Agent Expressions
33109 F.3 Using Agent Expressions
33112 Agent expressions can be used in several different ways by GDB, and the
33121 Another way to use agent expressions is for tracepoint data
33129 * The user specifies expressions to evaluate at each trace point.
33130 These expressions may denote objects in memory, in which case
33134 * GDB transmits the tracepoints and their associated expressions to
33140 evaluates the expressions associated with that trace point, and
33151 File: gdb.info, Node: Varying Target Capabilities, Next: Rationale, Prev: Using Agent Expressions, Up: Agent Expressions
33174 * maximum acceptable length of bytecode expressions
33182 File: gdb.info, Node: Rationale, Prev: Varying Target Capabilities, Up: Agent Expressions
33283 (there are no loops in expressions), so I never know the target
33338 File: gdb.info, Node: Target Descriptions, Next: Operating System Information, Prev: Agent Expressions, Up: Top
35585 * ambiguous expressions: Ambiguous Expressions.
35610 * arrays in expressions: Expressions. (line 14)
35746 * C++ compilers: C Plus Plus Expressions.
35768 * call overloaded functions: C Plus Plus Expressions.
35780 * casts, in expressions: Expressions. (line 28)
35781 * casts, to view memory: Expressions. (line 43)
35961 * debug formats and C++: C Plus Plus Expressions.
35968 * debugging C++ programs: C Plus Plus Expressions.
36059 * display of expressions: Auto Display. (line 6)
36194 * expressions: Expressions. (line 6)
36195 * expressions in Ada: Ada. (line 11)
36196 * expressions in C or C++: C. (line 6)
36197 * expressions in C++: C Plus Plus Expressions.
36199 * expressions in Modula-2: Modula-2. (line 12)
36265 * Fortran operators and expressions: Fortran Operators. (line 6)
36304 * GCC and C++: C Plus Plus Expressions.
36992 * member functions: C Plus Plus Expressions.
37005 * memory, viewing as typed object: Expressions. (line 43)
37046 * multiple-symbols menu: Ambiguous Expressions.
37058 * namespace in C++: C Plus Plus Expressions.
37130 * OpenCL C Expressions: OpenCL C Expressions.
37165 * overloaded functions, calling: C Plus Plus Expressions.
37480 * reference declarations: C Plus Plus Expressions.
37748 * set multiple-symbols: Ambiguous Expressions.
37948 * show multiple-symbols: Ambiguous Expressions.
38280 * this, inside C++ member functions: C Plus Plus Expressions.
38381 * type casting memory: Expressions. (line 43)
38385 * type conversions in C++: C Plus Plus Expressions.
38576 * {TYPE}: Expressions. (line 43)
38657 Node: Expressions253155
38658 Node: Ambiguous Expressions255247
38724 Node: C Plus Plus Expressions427715
38736 Node: OpenCL C Expressions441318
39074 Node: Agent Expressions1241795
39077 Node: Using Agent Expressions1261562
