* Info Catalog Up gdb: GDB/MI Command Syntax Next gdb: GDB/MI Output Syntax

gdb: GDB/MI Input Syntax

 
 27.2.1 GDB/MI Input Syntax
 --------------------------
 
 'COMMAND ==>'
      'CLI-COMMAND | MI-COMMAND'
 
 'CLI-COMMAND ==>'
      '[ TOKEN ] CLI-COMMAND NL', where CLI-COMMAND is any existing GDB
      CLI command.
 
 'MI-COMMAND ==>'
      '[ TOKEN ] "-" OPERATION ( " " OPTION )* [ " --" ] ( " " PARAMETER
      )* NL'
 
 'TOKEN ==>'
      "any sequence of digits"
 
 'OPTION ==>'
      '"-" PARAMETER [ " " PARAMETER ]'
 
 'PARAMETER ==>'
      'NON-BLANK-SEQUENCE | C-STRING'
 
 'OPERATION ==>'
      _any of the operations described in this chapter_
 
 'NON-BLANK-SEQUENCE ==>'
      _anything, provided it doesn't contain special characters such as
      "-", NL, """ and of course " "_
 
 'C-STRING ==>'
      '""" SEVEN-BIT-ISO-C-STRING-CONTENT """'
 
 'NL ==>'
      'CR | CR-LF'
 
 Notes:
 
    * The CLI commands are still handled by the MI interpreter; their
      output is described below.
 
    * The 'TOKEN', when present, is passed back when the command
      finishes.
 
    * Some MI commands accept optional arguments as part of the parameter
      list.  Each option is identified by a leading '-' (dash) and may be
      followed by an optional argument parameter.  Options occur first in
      the parameter list and can be delimited from normal parameters
      using '--' (this is useful when some parameters begin with a dash).
 
    Pragmatics:
 
    * We want easy access to the existing CLI syntax (for debugging).
 
    * We want it to be easy to spot a MI operation.
* Info Catalog Up gdb: GDB/MI Command Syntax Next gdb: GDB/MI Output Syntax