Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Chastain <mec.gnu@mindspring.com>
To: gdb-patches@sources.redhat.com, bob@brasko.net
Subject: Re: GDB/MI Output syntax
Date: Tue, 24 Aug 2004 19:33:00 -0000	[thread overview]
Message-ID: <412B980A.nailFLQ1QDS6L@mindspring.com> (raw)
In-Reply-To: <20040824191931.GC17542@white>

Bob Rossi <bob@brasko.net> wrote:
> -@code{@var{async-record} | @var{stream-record}}
> +@code{( @var{async-record} | @var{stream-record} ) @var{nl}}

I'm dubious about this.

stream-record does not have an NL terminator and needs one, yes.

But async-record already gets an NL terminator in the grammar
and does not need a second one.

  async-record -> exec-async-output | status-async-output | notify-async-output
  exec-async-output -> [token] "*" async-output
  async-output -> async-class ("," result)* nl

For example, gdb.mi/gdb669.exp gives:

  # gdb.log excerpt
  ~"[Thread debugging using libthread_db enabled]\n"
  ~"[New Thread 8192 (LWP 26606)]\n"
  ~"[Switching to Thread 8192 (LWP 26606)]\n"
  000*stopped,reason="breakpoint-hit",bkptno="1",thread-id="1",frame={addr="0x0804852d",func="main",args=[{name="argc",value="1"},{name="argv",value="0xbffff814"}],file="/berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.mi/pthreads.c",line="81"}
  (gdb) 


  reply	other threads:[~2004-08-24 19:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 19:19 Bob Rossi
2004-08-24 19:33 ` Michael Chastain [this message]
2004-08-24 19:39   ` Bob Rossi
2004-08-24 19:43     ` Bob Rossi
2004-08-24 19:53     ` Michael Chastain
2004-08-24 19:48   ` Andrew Cagney
2004-08-24 19:54     ` Bob Rossi
2004-08-24 20:01     ` Bob Rossi
2004-08-24 20:18       ` Andrew Cagney
2004-08-24 20:56         ` Bob Rossi
2004-08-25 15:51           ` Andrew Cagney
2004-08-25  4:09 ` Eli Zaretskii

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=412B980A.nailFLQ1QDS6L@mindspring.com \
    --to=mec.gnu@mindspring.com \
    --cc=bob@brasko.net \
    --cc=gdb-patches@sources.redhat.com \
    /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