Lines Matching full:interpreter
932 `-interpreter INTERP'
933 Use the interpreter INTERP for interface with the controlling
938 `--interpreter=mi' (or `--interpreter=mi2') causes GDB to use the
941 GDB version 5.3 and selected with `--interpreter=mi1', is
966 1. Sets up the command interpreter as specified by the command line
967 (*note interpreter: Mode Options.).
14122 interpreter (sometimes called the command-line interpreter or CLI) and
14123 the machine interface interpreter (or GDB/MI). This manual describes
14126 By default, GDB will start with the console interpreter. However,
14127 the user may choose to start GDB with another interpreter by specifying
14128 the `-i' or `--interpreter' startup options. Defined interpreters
14132 The traditional console or command-line interpreter. This is the
14133 most often used interpreter with GDB. With no interpreter
14134 specified at runtime, GDB will use this interpreter.
14148 The interpreter being used by GDB may not be dynamically switched at
14151 "interpreter-set console" in a console view, GDB would switch to using
14152 the console interpreter, rendering the IDE inoperable!
14154 Although you may only choose a single interpreter at startup, you
14155 may execute commands in any interpreter from the current interpreter
14157 interpreter, simply use the `interpreter-exec' command:
14159 interpreter-exec mi "-data-list-register-names"
14675 activated by specifying using the `--interpreter' command line option
14778 * The CLI commands are still handled by the MI interpreter; their
14931 recommended that front ends use the `-interpreter-exec' command (*note
14932 -interpreter-exec::).
18361 The `-interpreter-exec' Command
18367 -interpreter-exec INTERPRETER COMMAND
18369 Execute the specified COMMAND in the given INTERPRETER.
18374 The corresponding GDB command is `interpreter-exec'.
18380 -interpreter-exec console "break main"
21774 COMMAND (hex encoded) is passed to the local interpreter for
21779 stubs's interpreter may have security implications_.
23460 memory reference operations. The bytecode interpreter operates
23463 symbols; thus, the interpreter's internal data structures are simple,
23465 implement it. The interpreter is small, and strict limits on the
23472 * General Bytecode Design:: Overview of the interpreter.
23491 The bytecode interpreter is a stack-based machine; most instructions
23508 By the time the bytecode interpreter reaches the end of the
23515 Separate from the stack, the interpreter has two registers:
23547 If the interpreter is unable to evaluate an expression completely for
23550 This means that the problem is reported back to the interpreter's caller
24087 I want to keep the interpreter small, and we don't need them. We
24144 The interpreter has the base address around anyway for PC bounds
24180 Don't the `trace' bytecodes make the interpreter less general?
24181 They do mean that the interpreter contains special-purpose code,
24182 but that doesn't mean the interpreter can only be used for that
25048 * --interpreter: Mode Options. (line 141)
25163 * -interpreter-exec: GDB/MI Miscellaneous Commands.
25524 * console interpreter: Interpreters. (line 21)
26047 * interpreter-exec: Interpreters. (line 43)
26055 * invoke another interpreter: Interpreters. (line 37)
26255 * mi interpreter: Interpreters. (line 26)
26256 * mi1 interpreter: Interpreters. (line 34)
26257 * mi2 interpreter: Interpreters. (line 31)
27584 Ref: -interpreter-exec669957
