Lines Matching full:interpreter
971 `-interpreter INTERP'
972 Use the interpreter INTERP for interface with the controlling
977 `--interpreter=mi' (or `--interpreter=mi2') causes GDB to use the
980 GDB version 5.3 and selected with `--interpreter=mi1', is
1012 1. Sets up the command interpreter as specified by the command line
1013 (*note interpreter: Mode Options.).
4435 command interpreter, and it would be confusing if GDB unexpectedly
17774 Path in order to allow the Python interpreter to locate all scripts
17790 GDB provides one command for accessing the Python interpreter, and one
17822 interpreter:
20402 interpreter (sometimes called the command-line interpreter or CLI) and
20403 the machine interface interpreter (or GDB/MI). This manual describes
20406 By default, GDB will start with the console interpreter. However,
20407 the user may choose to start GDB with another interpreter by specifying
20408 the `-i' or `--interpreter' startup options. Defined interpreters
20412 The traditional console or command-line interpreter. This is the
20413 most often used interpreter with GDB. With no interpreter
20414 specified at runtime, GDB will use this interpreter.
20428 The interpreter being used by GDB may not be dynamically switched at
20431 "interpreter-set console" in a console view, GDB would switch to using
20432 the console interpreter, rendering the IDE inoperable!
20434 Although you may only choose a single interpreter at startup, you
20435 may execute commands in any interpreter from the current interpreter
20437 interpreter, simply use the `interpreter-exec' command:
20439 interpreter-exec mi "-data-list-register-names"
20692 has been started with the machine interface interpreter (*note The
20954 activated by specifying using the `--interpreter' command line option
21247 * The CLI commands are still handled by the MI interpreter; their
21402 recommended that front ends use the `-interpreter-exec' command (*note
21403 -interpreter-exec::).
25875 The `-interpreter-exec' Command
25881 -interpreter-exec INTERPRETER COMMAND
25882 Execute the specified COMMAND in the given INTERPRETER.
25887 The corresponding GDB command is `interpreter-exec'.
25893 -interpreter-exec console "break main"
30013 COMMAND (hex encoded) is passed to the local interpreter for
30018 stubs's interpreter may have security implications_.
32679 memory reference operations. The bytecode interpreter operates
32682 symbols; thus, the interpreter's internal data structures are simple,
32684 implement it. The interpreter is small, and strict limits on the
32691 * General Bytecode Design:: Overview of the interpreter.
32708 The bytecode interpreter is a stack-based machine; most instructions
32725 By the time the bytecode interpreter reaches the end of the
32732 Separate from the stack, the interpreter has two registers:
32764 If the interpreter is unable to evaluate an expression completely for
32767 This means that the problem is reported back to the interpreter's caller
33217 I want to keep the interpreter small, and we don't need them. We
33274 The interpreter has the base address around anyway for PC bounds
33310 Don't the `trace' bytecodes make the interpreter less general?
33311 They do mean that the interpreter contains special-purpose code,
33312 but that doesn't mean the interpreter can only be used for that
34144 interpreter used to run it.
35263 * --interpreter: Mode Options. (line 147)
35386 * -interpreter-exec: GDB/MI Miscellaneous Commands.
35892 * console interpreter: Interpreters. (line 21)
36722 * interpreter-exec: Interpreters. (line 43)
36733 * invoke another interpreter: Interpreters. (line 37)
37011 * mi interpreter: Interpreters. (line 26)
37012 * mi1 interpreter: Interpreters. (line 34)
37013 * mi2 interpreter: Interpreters. (line 31)
38936 Ref: -interpreter-exec992868
