From: "Eli Zaretskii" <eliz@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: kostik@ispras.ru, gdb@sources.redhat.com
Subject: Re: complete GDB MI specification
Date: Tue, 07 Dec 2004 21:47:00 -0000 [thread overview]
Message-ID: <01c4dca6$Blat.v2.2.2$806fa9e0@zahav.net.il> (raw)
In-Reply-To: <20041207195019.GB12487@white> (message from Bob Rossi on Tue, 7 Dec 2004 14:50:19 -0500)
> Date: Tue, 7 Dec 2004 14:50:19 -0500
> From: Bob Rossi <bob@brasko.net>
> Cc: kostik@ispras.ru, gdb@sources.redhat.com
>
> What I meant to say was, It would be helpful if there was a place in the
> GDB manual that had all of the MI commands for specific versions of MI,
> and all of the fields that the MI command is capable of outputting.
> Basically, the semantic information needed to write a parser and quickly
> interpret the MI commands as correct or incorrect output, and what each
> field means.
Such information, if we decide to include it, should go into
gdbint.texinfo.
But basically, I think that once the Yacc parser is written and
becomes part of GDB, we should maintain the parser instead of
documenting the grammar.
next prev parent reply other threads:[~2004-12-07 21:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 14:06 (a?)synchronous stepping commands in gdb MI, a week later Konstantin Karganov
2004-11-29 16:08 ` Andrew Cagney
2004-11-29 19:59 ` Re[2]: " Konstantin Karganov
2004-12-06 16:19 ` complete GDB MI specification Konstantin Karganov
2004-12-06 20:55 ` Eli Zaretskii
2004-12-07 18:42 ` Re[2]: " Konstantin Karganov
2004-12-07 18:58 ` Bob Rossi
2004-12-07 19:45 ` Eli Zaretskii
2004-12-07 19:50 ` Bob Rossi
2004-12-07 21:47 ` Eli Zaretskii [this message]
2004-12-07 19:42 ` Eli Zaretskii
2004-12-08 16:42 ` Re[2]: " Konstantin Karganov
2004-12-08 16:53 ` Bob Rossi
2004-12-08 17:45 ` Re[2]: " Konstantin Karganov
2004-12-08 18:30 ` Bob Rossi
2004-12-08 18:34 ` Bob Rossi
2004-12-08 18:39 ` Re[2]: " Konstantin Karganov
2004-12-08 17:01 ` Dave Korn
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='01c4dca6$Blat.v2.2.2$806fa9e0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=bob@brasko.net \
--cc=gdb@sources.redhat.com \
--cc=kostik@ispras.ru \
/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