From: Phil Muldoon <pmuldoon@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: GDB interface: MI versus API or ??
Date: Mon, 14 Jul 2008 20:25:00 -0000 [thread overview]
Message-ID: <487BB61E.7020104@redhat.com> (raw)
In-Reply-To: <487BB46C.4060007@redhat.com>
Keith Seitz wrote:
> Phil Muldoon wrote:
>
>> To be honest, I think eventually whatever we come up with, if it is
>> not improving GDB,
>> we'll end up at last emulating an MI interface. Just because
>> everything uses it already.
>
> Almost certainly something MI-like, indeed. There is definitely a need
> for a wire protocol for certain environments.
>
> I'm just playing devil's advocate. [Remembering the uproar it caused
> on the GDB mailing list a few years back, perhaps I should just keep
> to myself...]
>
> Keith
It think the (devil) advocate argument is a valuable one. I brought one
up earlier. I certainly value it; lets talk about the idea on its real
or theoretical merits. A deeper questions is why the folks over at CDT
think the MI protocol is ideal? Is it software conservatism? Is it
familiarity? Is it good-enough? Is MI good-enough to implement of of
most debugging problems? What are the limitations of MI?
Normally I find the edge-cases are the killers. Like someone who needs
to suck up 2G though the protocol straw, or various other extreme
drivers. Are they worthwhile cases? Do CDT have these cases?
It's all good. Lets think of them now while we are still in the thinking
stage ;)
Regards
Phil
next prev parent reply other threads:[~2008-07-14 20:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 14:38 Rick Moseley
2008-07-14 16:44 ` Phil Muldoon
2008-07-14 18:59 ` Rick Moseley
2008-07-14 19:11 ` Tom Tromey
2008-07-14 19:31 ` Rick Moseley
2008-07-14 20:01 ` Keith Seitz
2008-07-14 20:10 ` Daniel Jacobowitz
2008-07-14 20:11 ` Phil Muldoon
2008-07-14 20:18 ` Keith Seitz
2008-07-14 20:25 ` Phil Muldoon [this message]
2008-07-14 19:30 ` Rick Moseley
2008-07-15 15:30 ` Sami Wagiaalla
2008-07-16 17:08 ` Dodji Seketeli
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=487BB61E.7020104@redhat.com \
--to=pmuldoon@redhat.com \
--cc=frysk@sourceware.org \
--cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).