public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
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:11:00 -0000	[thread overview]
Message-ID: <487BB2D4.1090702@redhat.com> (raw)
In-Reply-To: <487BB090.1010807@redhat.com>

Keith Seitz wrote:
> Rick Moseley wrote:
>>> To me those responses pretty much indicated that the CDT developers do
>>> not see MI as a limiter.
>>>   
>> My thoughts exactly.
>
> Is that really true, though? Do they have any other choice but gdb/MI?
>
> The responses sound more like they welcome a "better"/enhanced 
> debugger backend (who wouldn't), but they've got a good, mature 
> product and plenty of other work to do, too. So MI is "good enough".
>
> We shouldn't confuse "good" with "good enough". But perhaps the cynic 
> is me needs to be beaten into submission again.

That's my read too. Just because they have MI and it works, does it mean 
that it could be improved on? Bettered? But unless we come up with a 
better way, then automatically we're just quoting optimistic theory over 
actual implementation.  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.

Regards

Phil

  parent reply	other threads:[~2008-07-14 20:11 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 [this message]
2008-07-14 20:18             ` Keith Seitz
2008-07-14 20:25               ` Phil Muldoon
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=487BB2D4.1090702@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).