Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: asmwarrior <asmwarrior@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: GDB Development <gdb@sourceware.org>
Subject: Re: document issue about GDB/MI output syntax
Date: Fri, 20 Dec 2013 01:25:00 -0000	[thread overview]
Message-ID: <52B39C3D.9000805@gmail.com> (raw)
In-Reply-To: <20131219180743.GJ26143@adacore.com>

On 2013-12-20 2:07, Joel Brobecker wrote:
>> Hi, I just found in this page:
>> https://sourceware.org/gdb/current/onlinedocs/gdb/GDB_002fMI-Output-Syntax.html#GDB_002fMI-Output-Syntax
>> The syntax is not correct:
>>
>> console-stream-output ==>
>>     "~" c-string
>> target-stream-output ==>
>>     "@" c-string
>> log-stream-output ==>
>>     "&" c-string 
>>
>> It should be:
>>
>> console-stream-output ==>
>>     "~" c-string nl
>> target-stream-output ==>
>>     "@" c-string nl
>> log-stream-output ==>
>>     "&" c-string nl
>>
>> There is a "nl" missing in those stream-record, right?
> 
> I haven't verified with actual behavior, but something doesn't
> look right indeed. 

Here is the log I start gdb in MI under Windows


E:\code\opencv\debugxb>gdb --interpreter=mi
=thread-group-added,id="i1"
~"GNU gdb (GDB) 7.6.50.20131219-cvs\n"
~"Copyright (C) 2013 Free Software Foundation, Inc.\n"
~"License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\
nThis is free software: you are free to change and redistribute it.\nThere is NO
 WARRANTY, to the extent permitted by law.  Type \"show copying\"\nand \"show wa
rranty\" for details.\n"
~"This GDB was configured as \"mingw32\".\nType \"show configuration\" for confi
guration details."
~"\nFor bug reporting instructions, please see:\n"
~"<http://www.gnu.org/software/gdb/bugs/>.\n"
~"Find the GDB manual and other documentation resources online at:\n<http://www.
gnu.org/software/gdb/documentation/>.\n"
~"For help, type \"help\".\n"
~"Type \"apropos word\" to search for commands related to \"word\".\n"
(gdb)


You see there are "nl"s after each line of GDB's message.


However, I am wondering if we shouldn't
> put the "nl" at the end of each [...]-record rule. Looking
> at the grammar as currently written, I think we have issues
> with other records.
> 

I think the "nl" can be put in a high level rule. E.g.

out-of-band-record ==>
    (async-record | stream-record) "nl"

I'm not sure the above grammar is in correct format, just put the "nl" in the end of out-of-band-record.

Yuanhui Zhang


  reply	other threads:[~2013-12-20  1:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19  7:55 asmwarrior
2013-12-19 18:07 ` Joel Brobecker
2013-12-20  1:25   ` asmwarrior [this message]
2013-12-20  3:38     ` 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=52B39C3D.9000805@gmail.com \
    --to=asmwarrior@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@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