This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
gdb/mi add section documenting proposed syntax changes
- To: GDB Patches <gdb-patches at sourceware dot cygnus dot com>
- Subject: gdb/mi add section documenting proposed syntax changes
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Wed, 26 Apr 2000 19:18:48 +1000
- Organization: Cygnus Solutions
Hello,
The attached updates gdb/mi/gdbmi.texinfo so that the proposed changes
to the syntax are included in the manual.
It is intended as a heads up so that users are aware that the change
may, eventually, occure.
Andrew
Look ok? branch?
Wed Apr 26 18:35:19 2000 Andrew Cagney <cagney@b1.cygnus.com>
* gdbmi.texinfo (GDB/MI Output Syntax v2.0): Convert Draft 2.0
Output Syntax into a new section. Cross reference.
(menu): Fix tipo. GDB/MI Compatibility with CLI.
Index: gdbmi.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/mi/gdbmi.texinfo,v
retrieving revision 1.2.2.1
diff -p -r1.2.2.1 gdbmi.texinfo
*** gdbmi.texinfo 2000/04/23 09:14:05 1.2.2.1
--- gdbmi.texinfo 2000/04/26 09:14:34
*************** Elena Zannoni.
*** 104,110 ****
@menu
* GDB/MI Command Syntax::
! * GDB/MI and CLI::
* GDB/MI Output Records::
* GDB/MI Command Description Format::
* GDB/MI Breakpoint Table Commands::
--- 104,110 ----
@menu
* GDB/MI Command Syntax::
! * GDB/MI Compatibility with CLI::
* GDB/MI Output Records::
* GDB/MI Command Description Format::
* GDB/MI Breakpoint Table Commands::
*************** Elena Zannoni.
*** 117,122 ****
--- 117,123 ----
* GDB/MI Thread Commands::
* GDB/MI Tracepoint Commands::
* GDB/MI Variable Objects::
+ * GDB/MI Draft 2.0 Output Syntax::
@end menu
@c When these are implemented, they should be moved to be between Misc and
*************** the log output is prefixed by @samp{&}.
*** 340,345 ****
--- 341,349 ----
@xref{GDB/MI Stream Records, , @sc{gdb/mi} Stream Records}, for more
details about the various output records.
+ @xref{GDB/MI Draft 2.0 Output Syntax, , @sc{gdb/mi} Draft 2.0 Output
+ Syntax}, for proposed revisions to the current output syntax.
+
@node GDB/MI Simple Examples
@subsection Simple Examples of @sc{gdb/mi} Interaction
@cindex @sc{gdb/mi}, simple examples
*************** Here's what happens if you pass a non-ex
*** 396,402 ****
@end example
@c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
! @node GDB/MI and CLI
@section @sc{gdb/mi} Compatibility with CLI
@cindex compatibility, @sc{gdb/mi} and CLI
--- 400,406 ----
@end example
@c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
! @node GDB/MI Compatibility with CLI
@section @sc{gdb/mi} Compatibility with CLI
@cindex compatibility, @sc{gdb/mi} and CLI
*************** Update the value of the variable object
*** 3732,3744 ****
expression after fetching all the new values from memory or registers.
A @samp{*} causes all existing variable objects to be updated.
! @ignore
! @c%%%%%%%%%%%%%%%%%%%%%%%%%%%% APPENDIX %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
! @appendix Proposed v2.0 Output Syntax
! This appendix is not part of the MI specification. It is provided as a
! discussion point.
The output from @sc{gdb/mi} consists of zero or more out-of-band records
optionally followed by a single result record. The result record being
for the most recent command input. The sequence being terminated by
--- 3736,3767 ----
expression after fetching all the new values from memory or registers.
A @samp{*} causes all existing variable objects to be updated.
! @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
! @node GDB/MI Draft 2.0 Output Syntax
! @section @sc{gdb/mi} Draft 2.0 Output Syntax
!
! @cindex draft 2.0 output syntax of @sc{gdb/mi}
! @cindex @sc{gdb/mi}, draft 2.0 output syntax
!
! One problem identified in the existing @sc{gdb/mi} output syntax was the
! difficulty in differentiating between a tuple such as:
!
! @example
! @{number="1",type="breakpoint",disp="keep",enabled="y"@}
! @end example
! where each value has a unique label, and a list such as:
+ @example
+ @{"1","2","4"@}
+ @{bp="1",bp="2",bp="4"@}
+ @end example
+
+ where values are un-labeled or the label is duplicated.
+
+ What follows is a draft revision to the output specification that
+ addresses this problem.
+
The output from @sc{gdb/mi} consists of zero or more out-of-band records
optionally followed by a single result record. The result record being
for the most recent command input. The sequence being terminated by
*************** instance messages that should be display
*** 3870,3878 ****
the log output is prefixed by the prefix ``&''.
@end itemize
-
- @end ignore
-
@c Local variables:
@c change-log-default-name: "ChangeLog-mi"
--- 3893,3898 ----