Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob_rossi@cox.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: CLI and GDB/MI documentation patch
Date: Fri, 12 May 2006 14:30:00 -0000	[thread overview]
Message-ID: <20060512142135.GG26655@brasko.net> (raw)
In-Reply-To: <ulkt7738t.fsf@gnu.org>

On Fri, May 12, 2006 at 04:59:46PM +0300, Eli Zaretskii wrote:
> > Date: Fri, 12 May 2006 08:54:33 -0400
> > From: Bob Rossi <bob_rossi@cox.net>
> > Cc: gdb-patches@sources.redhat.com
> > 
> > Old versions of mi2 will act incorrectly, where as new versions of mi2 
> > will work better.
> 
> In what release of GDB were those problems fixed?

I'm not sure if it helps to think of things in terms of releases in
regards to GDB/MI. Unfortunatly, many distros package a CVS release of
GDB. So, any given snapshot of GDB could have this feature or not.

However, with that said, Nick posted this:

    2005-02-20  Andrew Cagney  <cagney@gnu.org>

            * mi/mi-main.c (captured_mi_execute_command): Use
            mi_cmd_interpreter_exec.

So I believe that's the day when it started working nice. Eli, the real
problem is, mi2 is the currently supported protocol, and certain
versions of mi2 work and certain version don't, so I'm not sure this is
a historical issue.

> > Well, first off, this is incorrect:
> > 
> >     This mechanism is provided as an aid to developers of @sc{gdb/mi}
> >     clients and not as a reliable interface into the CLI.
> 
> What would you suggest to say instead?  In your patch, all you did
> was add the word ``originally'':
> 
>   This mechanism was originally provided as an aid to developers of @sc{gdb/mi}
>   clients and not as a reliable interface into the CLI. The output of these
> 
> But you never say what's its role _now_.

I thought I did, but apparently I was unclear. The next 2 paragraphs
were supposed to describe what it's role is now, I'm sorry to see it was
written so unclear.

Bob Rossi


  reply	other threads:[~2006-05-12 14:21 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-12  1:16 Bob Rossi
2006-05-12  7:53 ` Eli Zaretskii
2006-05-12  8:14   ` Vladimir Prus
2006-05-12 11:30     ` Eli Zaretskii
2006-05-12 13:56       ` Bob Rossi
2006-05-12 12:49   ` Daniel Jacobowitz
2006-05-12 12:54     ` Daniel Jacobowitz
2006-05-12 13:58     ` Eli Zaretskii
2006-05-12 14:02       ` Daniel Jacobowitz
2006-05-12 14:10         ` Bob Rossi
2006-05-12 18:32           ` Eli Zaretskii
2006-05-12 18:37         ` Eli Zaretskii
2006-05-12 18:55           ` Daniel Jacobowitz
2006-05-12 19:01             ` Eli Zaretskii
2006-05-12 19:16               ` Daniel Jacobowitz
2006-05-12 19:51                 ` Bob Rossi
2006-05-13  9:28                 ` Eli Zaretskii
2006-05-15 15:50                   ` Daniel Jacobowitz
2006-05-12 20:26               ` PAUL GILLIAM
2006-05-13  8:45                 ` Eli Zaretskii
2006-05-12 12:59   ` Bob Rossi
2006-05-12 14:12     ` Eli Zaretskii
2006-05-12 14:30       ` Bob Rossi [this message]
2006-05-12 18:28         ` Eli Zaretskii
2006-05-12 19:19           ` Bob Rossi
2006-05-13  8:09             ` Eli Zaretskii
2006-05-13 11:02               ` Bob Rossi
2006-05-13 14:29                 ` Eli Zaretskii
2006-05-29 19:05           ` Bob Rossi
2006-05-30  7:17             ` Eli Zaretskii
2006-05-12 12:44 Nick Roberts
2006-05-12 14:19 ` Eli Zaretskii
2006-05-12 16:42   ` Bob Rossi
2006-05-12 22:14   ` Nick Roberts
2006-05-12 22:19     ` Bob Rossi
2006-05-13  9:13       ` Nick Roberts
2006-05-13 16:04         ` Daniel Jacobowitz

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=20060512142135.GG26655@brasko.net \
    --to=bob_rossi@cox.net \
    --cc=eliz@gnu.org \
    --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