From: Pawel Piech <pawel.piech@windriver.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sources.redhat.com
Subject: Re: MI non-stop interface details
Date: Thu, 01 May 2008 18:37:00 -0000 [thread overview]
Message-ID: <481A0D71.8090801@windriver.com> (raw)
In-Reply-To: <200805012211.51656.vladimir@codesourcery.com>
Vladimir Prus wrote:
> GDB/MI is actually not a finished published protocol -- it's work in progress.
> Unfortunately, frontend maintainers tended to read between the lines, and guess
> the behaviour and accepted input instead of asking here. And in cases where what
> they've read between the lines does not correspond to what GDB developers means,
> the result is a buggy frontend :-)
>
> Given that MI, presently, is still not adequate for such basic tasks as
> listing local variables in a function, it will change, and it might break
> things, and frontend developers should provide the input to avoid surprises.
> You and Marc represent Eclipse here, and Nick represent Emacs, and
> I represent KDevelop, so those three are fine, but other frontend developers
> should be more active here.
>
> Probably, I should add big warning to MI manual, saying that everything that is not
> 100% clear must be asked on the list.
>
> - Volodya
>
Given how long (and for how many versions) GDB/MI has been around and
how long it's been used by clients, you cannot simply make a disclaimer
and change it at will without negative consequences to clients and
indirectly to GDB. It's kind of like common law marriage. Common law
marriage is a law in most states in the U.S. where if you live as a
couple in the same house for so many years, you become legally married
even if you never said the vows. :-)
Cheers,
Pawel
next prev parent reply other threads:[~2008-05-01 18:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 18:09 Vladimir Prus
2008-04-26 18:16 ` Doug Evans
2008-04-26 19:49 ` Vladimir Prus
2008-04-30 7:18 ` Marc Khouzam
2008-04-28 16:21 ` Pedro Alves
2008-04-29 19:21 ` Vladimir Prus
2008-04-29 20:04 ` Pedro Alves
2008-04-30 7:00 ` Pawel Piech
2008-05-01 16:15 ` Vladimir Prus
2008-05-01 16:31 ` Pawel Piech
2008-05-01 16:38 ` Vladimir Prus
2008-05-01 16:58 ` Pawel Piech
[not found] ` <4819F4D4.4010305@windriver.com>
2008-05-01 17:00 ` Vladimir Prus
2008-05-01 17:53 ` Pawel Piech
2008-05-01 18:12 ` Vladimir Prus
2008-05-01 18:37 ` Pawel Piech [this message]
2008-05-02 1:23 ` Evolution of GDB/MI [was Re: MI non-stop interface details] Nick Roberts
2008-04-30 14:23 ` MI non-stop interface details Marc Khouzam
2008-04-30 17:21 ` Pedro Alves
[not found] ` <200804301117.42633.vladimir@codesourcery.com>
[not found] ` <4818AA58.4040201@windriver.com>
2008-05-01 17:11 ` Vladimir Prus
2008-05-01 18:08 ` Pawel Piech
2008-05-02 14:21 ` Vladimir Prus
2008-05-02 16:59 ` Pawel Piech
2008-05-02 17:13 ` Vladimir Prus
[not found] ` <481B4FDC.4010802@windriver.com>
2008-05-02 17:36 ` Vladimir Prus
2008-05-02 18:00 ` Pawel Piech
2008-05-02 18:19 ` Vladimir Prus
2008-05-02 18:36 ` Pawel Piech
2008-04-29 3:14 ` Pawel Piech
[not found] ` <200804301059.44112.vladimir@codesourcery.com>
[not found] ` <200804301534.48779.pedro@codesourcery.com>
2008-05-01 17:22 ` Vladimir Prus
2008-05-01 17:52 ` Pedro Alves
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=481A0D71.8090801@windriver.com \
--to=pawel.piech@windriver.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