Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sources.redhat.com
Subject: Re: Turnaround upgrade in mi2
Date: Sun, 10 Jan 2010 18:17:00 -0000	[thread overview]
Message-ID: <4B4A1DAA.1030006@gmail.com> (raw)
In-Reply-To: <hid390$sir$1@ger.gmane.org>

Vladimir Prus wrote:
> Sean Chen wrote:
> 
>> Hi,
>>
>> I compared the two versions of MI (mi1 and mi2) but found no obvious
>> syntax change except some new commands. I think, personally, if there
>> is no turnaround upgrade in gdb 6.0, 
> 
> What is "turnaround upgrade"?

  I'm inferring it means any kind of back-compat break.

> 
>> why did we need to accumulate the
>> version number to mi2? You know, there are also many new commands in
>> gdb 7.0, but we don’t accumulate the mi version number to mi3 in gdb
>> 7.0.
>>
>> So I am prone to think I must have missed the turnaround upgrade in
>> mi2. Could somebody help to clarify? Thanks.
> 
> I am afraid I don't know what are the differences between mi1 and mi2 and I am
> not sure it's worth investigating. 

  I have a vague memory that the difference is how asynchronous output from
the inferior is presented in the output stream, and that the difference was
enough to make it impossible to unambiguously parse an mi stream without
knowing which one you were dealing with in advance.  Sorry, I have no
reference, but I'm sure there was a sane reason, I think it was to do with the
output format and its parseability, and so it wouldn't have been just because
new commands were added.

    cheers,
      DaveK


  reply	other threads:[~2010-01-10 18:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-10 16:03 Sean Chen
2010-01-10 17:39 ` Vladimir Prus
2010-01-10 18:17   ` Dave Korn [this message]
2010-01-10 21:09     ` 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=4B4A1DAA.1030006@gmail.com \
    --to=dave.korn.cygwin@googlemail.com \
    --cc=gdb@sources.redhat.com \
    --cc=vladimir@codesourcery.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