212 Chapter 26. The gdb/mi Interface"^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-stringThe operation failed. The c-string contains the corresponding error message.26.6.2. gdb/mi Stream Recordsgdb internally maintains a number of output streams: the console, the target, and the log. The outputintended 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 (refer to Section26.4.2 gdb/mi Output Syntax). 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 animplicit newline)."~" string-outputThe console output stream contains text that should be displayed in the CLI console window. Itcontains the textual responses to CLI commands."@" string-outputThe target output stream contains any textual output from the running target."&" string-outputThe log stream contains debugging messages being produced by gdb’s internals.26.6.3. gdb/mi Out-of-band RecordsOut-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 (e.g., a breakpoint modified) or a result oftarget activity (e.g., target stopped).The following is a preliminary list of possible out-of-band records."*" "stop"stop26.7. gdb/mi Command Description FormatThe remaining sections describe blocks of commands. Each block of commands is laid out in a fashionsimilar to this section.Note the the line breaks shown in the examples are here only for readability. They don’t appear inthe real output. Also note that the commands with a non-available example (N.A.) are not yet imple-mented.
