Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: Konstantin Karganov <kostik@ispras.ru>
Cc: gdb@sources.redhat.com
Subject: Re: complete GDB MI specification
Date: Tue, 07 Dec 2004 19:42:00 -0000	[thread overview]
Message-ID: <01c4dc95$Blat.v2.2.2$0f2f1c40@zahav.net.il> (raw)
In-Reply-To: <429477215.20041207214436@ispras.ru> (message from Konstantin Karganov on Tue, 7 Dec 2004 21:44:36 +0300)

> Date: Tue, 7 Dec 2004 21:44:36 +0300
> From: Konstantin Karganov <kostik@ispras.ru>
> CC: gdb@sources.redhat.com
> 
> "Note that the current ``grammar'' in the MI documentation, at least as
> far as I'm concerned, is meant to be an informal introduction of the
> MI syntax, not a rigurous grammar description.

This is known, of course.  Volunteers are welcome to rewrite the MI
documentation more rigorously.  I was happy enough to get my hands on
_any_ documentation, and needed to do non-trivial amounts of work to
bring it to the state where it could be integrated into gdb.texinfo.

> And this is the problem! MI is supposed to be a program-to-program
> interface and thus needs a complete formal description (at least, to be
> sure that all possible output is handled correctly).

I agree, but no one volunteered yet to produce such a formal
description.  (And I'm not sure such a description should be in the
manual, anyway.)

> Looked through several (a lot, actually!) discussions and didn't found
> what I need.

Sorry, I thought a grammar was posted, but perhaps I was mistaken.

> > Please report all such unclear cases, and I will try to fix them.
> Look at the structure of MI description: there are the command syntax
> with explanation and the example of the output. Just an example
> instead of complete output specification. Yes, it fits the general case
> of " var=value (,var=value)* " syntax but the actual semantics and
> possible value pairs are not specified. That is for all commands.

If an example is clear and tells enough to explain what to expect,
then it's fine by me.  If you find incorrect or misleading examples,
please point them out, and please tell what is misleading about them.
I appreciate your comments, but to fix the manual, I need them to be
more specific.

> Anyway, it looks weird if no rigorous specification of MI output
> exist. IMHO it means (if it is) that no one uses MI in real systems
> (except the tests and demo purposes)...

Rest assured that it _is_ used, in real-life systems.


  parent reply	other threads:[~2004-12-07 19:42 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
2004-12-07 19:42           ` Eli Zaretskii [this message]
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='01c4dc95$Blat.v2.2.2$0f2f1c40@zahav.net.il' \
    --to=eliz@gnu.org \
    --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