From: asmwarrior <asmwarrior@gmail.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [RFC, doc] fix document error on the grammar of GDB/MI output format syntax
Date: Sun, 22 Dec 2013 07:38:00 -0000 [thread overview]
Message-ID: <52B69693.10107@gmail.com> (raw)
Hi, I noticed that GDB has a "new line" in the end of "out-of-band-record".
But the document does not correctly describe this. See here:
https://sourceware.org/gdb/current/onlinedocs/gdb/GDB_002fMI-Output-Syntax.html#GDB_002fMI-Output-Syntax
Some discussion has already in GDB maillist, see: https://sourceware.org/ml/gdb/2013-12/msg00058.html
As Joel suggested there that the change should be both reviewed by Eli and some GDB maintainer.
The change log could be: Fix syntax description error about GDB/MI "out-of-band-record", there should be a "new line" in end.
Thanks.
Yuanhui Zhang
gdb/doc/gdb.texinfo | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index b7551c2..a8b888c 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -29160,7 +29160,7 @@ corresponding output for that command will also be prefixed by that same
@code{ [ @var{token} ] "^" @var{result-class} ( "," @var{result} )* @var{nl}}
@item @var{out-of-band-record} @expansion{}
-@code{@var{async-record} | @var{stream-record}}
+@code{@var{async-record} @var{nl} | @var{stream-record} @var{nl}}
@item @var{async-record} @expansion{}
@code{@var{exec-async-output} | @var{status-async-output} | @var{notify-async-output}}
next reply other threads:[~2013-12-22 7:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 7:38 asmwarrior [this message]
2013-12-22 8:09 ` Joel Brobecker
2013-12-22 11:33 ` asmwarrior
2013-12-22 16:18 ` Eli Zaretskii
2013-12-23 0:41 ` Joel Brobecker
2013-12-23 1:18 ` asmwarrior
2013-12-23 1:29 ` Joel Brobecker
2013-12-23 1:39 ` asmwarrior
2014-01-15 12:23 ` [pushed] " Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52B69693.10107@gmail.com \
--to=asmwarrior@gmail.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox