OpenCores
URL https://opencores.org/ocsvn/or1k/or1k/trunk

Subversion Repositories or1k

[/] [or1k/] [trunk/] [gdb-5.0/] [gdb/] [doc/] [gdb.info-10] - Diff between revs 107 and 362

Go to most recent revision | Show entire file | Details | Blame | View Log

Rev 107 Rev 362
Line 1... Line 1...
This is ./gdb.info, produced by Makeinfo version 3.12f from gdb.texinfo.
This is ./gdb.info, produced by makeinfo version 4.0 from gdb.texinfo.
 
 
INFO-DIR-SECTION Programming & development tools.
INFO-DIR-SECTION Programming & development tools.
START-INFO-DIR-ENTRY
START-INFO-DIR-ENTRY
* Gdb: (gdb).                     The GNU debugger.
* Gdb: (gdb).                     The GNU debugger.
END-INFO-DIR-ENTRY
END-INFO-DIR-ENTRY
Line 24... Line 24...
   Permission is granted to copy and distribute translations of this
   Permission is granted to copy and distribute translations of this
manual into another language, under the above conditions for modified
manual into another language, under the above conditions for modified
versions.
versions.
 
 


File: gdb.info,  Node: GDB/MI Result Records,  Next: GDB/MI Stream Records,  Up: GDB/MI Output Records
 
 
 
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' is the return
 
     value.
 
 
 
`"^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.
 
 
 

 
File: gdb.info,  Node: GDB/MI Stream Records,  Next: GDB/MI Out-of-band Records,  Prev: GDB/MI Result Records,  Up: GDB/MI Output Records
 
 
 
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 (*note GDB/MI Output Syntax: 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 an implicit newline).
 
 
 
`"~" 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 debugging messages being produced by GDB's
 
     internals.
 
 
 

 
File: gdb.info,  Node: GDB/MI Out-of-band Records,  Prev: GDB/MI Stream Records,  Up: GDB/MI Output Records
 
 
 
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 (e.g., a breakpoint modified) or a result of
 
target activity (e.g., target stopped).
 
 
 
   The following is a preliminary list of possible out-of-band records.
 
 
 
`"*" "stop"'
 

 
File: gdb.info,  Node: GDB/MI Command Description Format,  Next: GDB/MI Breakpoint Table Commands,  Prev: GDB/MI Output Records,  Up: GDB/MI
File: gdb.info,  Node: GDB/MI Command Description Format,  Next: GDB/MI Breakpoint Table Commands,  Prev: GDB/MI Output Records,  Up: GDB/MI
 
 
GDB/MI Command Description Format
GDB/MI Command Description Format
=================================
=================================
 
 

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.