Filter
Top Products
21.3 GDB/MI output records
21.3.1 GDB/MI result records
In addition to a number of out-of-band notifications, the response to a GDB/MI command
includes one of the following result indications:
"^done" [ "," results ]
The synchronous operation was successful,
results are the return values.
"^running"
The asynchronous operation was successfully
started. The target is running.
"^error" "," c-string The operation failed. The c-string contains the
corresponding error message.
21.3.2 GDB/MI stream records
GDB internally maintains a number of output streams: the console, the target, and the
log. The output intended for each of these streams is funneled through the gdb/mi
interface using stream records.
Each stream record begins with a unique prefix character which identifies its stream (see
“GDB/MI Output syntax” (page 308)). In addition to the prefix, each stream record
contains a string-output. This is either raw text (with an implicit new line) or a
quoted C string (which does not contain an implicit new line).
"~" string-output
The console output stream contains text that should be
displayed in the CLI console window. It contains the textual
responses to CLI commands.
"@" string-output
The target output stream contains any textual output from
the running target.
"&" string-output
The log stream contains internal debugging messages being
produced by GDB.
21.3.3 GDB/MI out-of-band records
Out-of-band records are used to notify the GDB/MI client of additional changes that
have occurred. Those changes can either be a consequence of GDB/MI (for example, a
breakpoint modified) or a result of target activity (for example, target stopped).
The following is a preliminary list of possible out-of-band records.
"*" "stop"
21.4 GDB/MI command description format
The remaining sections describe blocks of commands. Each block of commands is laid
out in a fashion similar to this section.
21.3 GDB/MI output records 311