3 <title>Debugging with GDB
</title>
4 <meta http-equiv=
"Content-Type" content=
"text/html">
5 <meta name=
"description" content=
"Debugging with GDB">
6 <meta name=
"generator" content=
"makeinfo 4.3">
7 <link href=
"http://www.gnu.org/software/texinfo/" rel=
"generator-home">
12 Node:
<a name=
"GDB%2fMI%20Stream%20Records">GDB/MI Stream Records
</a>,
13 Next:
<a rel=
"next" accesskey=
"n" href=
"GDB-MI-Out-of-band-Records.html#GDB%2fMI%20Out-of-band%20Records">GDB/MI Out-of-band Records
</a>,
14 Previous:
<a rel=
"previous" accesskey=
"p" href=
"GDB-MI-Result-Records.html#GDB%2fMI%20Result%20Records">GDB/MI Result Records
</a>,
15 Up:
<a rel=
"up" accesskey=
"u" href=
"GDB-MI-Output-Records.html#GDB%2fMI%20Output%20Records">GDB/MI Output Records
</a>
19 <h4 class=
"subsection"><small>GDB/MI
</small> Stream Records
</h4>
21 GDB internally maintains a number of output streams: the console, the
22 target, and the log. The output intended for each of these streams is
23 funneled through the
<small>GDB/MI
</small> interface using
<dfn>stream records
</dfn>.
25 <p>Each stream record begins with a unique
<dfn>prefix character
</dfn> which
26 identifies its stream (see
<a href=
"GDB-MI-Output-Syntax.html#GDB%2fMI%20Output%20Syntax"><small>GDB/MI
</small> Output Syntax
</a>). In addition to the prefix, each stream record contains a
27 <code></code><var>string-output
</var><code></code>. This is either raw text (with an implicit new
28 line) or a quoted C string (which does not contain an implicit newline).
31 <dt><code>"~" </code><var>string-output
</var><code></code>
32 <dd>The console output stream contains text that should be displayed in the
33 CLI console window. It contains the textual responses to CLI commands.
35 <br><dt><code>"@" </code><var>string-output
</var><code></code>
36 <dd>The target output stream contains any textual output from the running
39 <br><dt><code>"&" </code><var>string-output
</var><code></code>
40 <dd>The log stream contains debugging messages being produced by GDB's