Lines Matching full:interpreter
958 `-interpreter INTERP'
959 Use the interpreter INTERP for interface with the controlling
964 `--interpreter=mi' (or `--interpreter=mi2') causes GDB to use the
967 GDB version 5.3 and selected with `--interpreter=mi1', is
992 1. Sets up the command interpreter as specified by the command line
993 (*note interpreter: Mode Options.).
4326 command interpreter, and it would be confusing if GDB unexpectedly
16627 GDB provides one command for accessing the Python interpreter, and one
16659 interpreter:
17793 interpreter (sometimes called the command-line interpreter or CLI) and
17794 the machine interface interpreter (or GDB/MI). This manual describes
17797 By default, GDB will start with the console interpreter. However,
17798 the user may choose to start GDB with another interpreter by specifying
17799 the `-i' or `--interpreter' startup options. Defined interpreters
17803 The traditional console or command-line interpreter. This is the
17804 most often used interpreter with GDB. With no interpreter
17805 specified at runtime, GDB will use this interpreter.
17819 The interpreter being used by GDB may not be dynamically switched at
17822 "interpreter-set console" in a console view, GDB would switch to using
17823 the console interpreter, rendering the IDE inoperable!
17825 Although you may only choose a single interpreter at startup, you
17826 may execute commands in any interpreter from the current interpreter
17828 interpreter, simply use the `interpreter-exec' command:
17830 interpreter-exec mi "-data-list-register-names"
18339 activated by specifying using the `--interpreter' command line option
18627 * The CLI commands are still handled by the MI interpreter; their
18782 recommended that front ends use the `-interpreter-exec' command (*note
18783 -interpreter-exec::).
22754 The `-interpreter-exec' Command
22760 -interpreter-exec INTERPRETER COMMAND
22761 Execute the specified COMMAND in the given INTERPRETER.
22766 The corresponding GDB command is `interpreter-exec'.
22772 -interpreter-exec console "break main"
26784 COMMAND (hex encoded) is passed to the local interpreter for
26789 stubs's interpreter may have security implications_.
29169 memory reference operations. The bytecode interpreter operates
29172 symbols; thus, the interpreter's internal data structures are simple,
29174 implement it. The interpreter is small, and strict limits on the
29181 * General Bytecode Design:: Overview of the interpreter.
29198 The bytecode interpreter is a stack-based machine; most instructions
29215 By the time the bytecode interpreter reaches the end of the
29222 Separate from the stack, the interpreter has two registers:
29254 If the interpreter is unable to evaluate an expression completely for
29257 This means that the problem is reported back to the interpreter's caller
29697 I want to keep the interpreter small, and we don't need them. We
29754 The interpreter has the base address around anyway for PC bounds
29790 Don't the `trace' bytecodes make the interpreter less general?
29791 They do mean that the interpreter contains special-purpose code,
29792 but that doesn't mean the interpreter can only be used for that
30580 interpreter used to run it.
31639 * --interpreter: Mode Options. (line 141)
31754 * -interpreter-exec: GDB/MI Miscellaneous Commands.
32205 * console interpreter: Interpreters. (line 21)
32874 * interpreter-exec: Interpreters. (line 43)
32885 * invoke another interpreter: Interpreters. (line 37)
33119 * mi interpreter: Interpreters. (line 26)
33120 * mi1 interpreter: Interpreters. (line 34)
33121 * mi2 interpreter: Interpreters. (line 31)
34813 Ref: -interpreter-exec868292
