From: Tom Tromey <tromey@redhat.com>
To: "Doug Evans" <dje@google.com>
Cc: gdb@sourceware.org
Subject: Re: GDB MI Interface
Date: Wed, 16 Apr 2008 09:47:00 -0000 [thread overview]
Message-ID: <m3iqyivfwu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <e394668d0804151346o28740f08h162a5dcbc8e37b55@mail.gmail.com> (Doug Evans's message of "Tue\, 15 Apr 2008 13\:46\:28 -0700")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> Is it lamentable that we have both gdbmi and (soon) a real scripting
Doug> interface with no real commonality? Just thinking out loud ... I
Doug> don't have an answer.
I worried about this a bit, particularly when hacking up the event
code to be able to notify python even when some other interpreter has
been chosen.
Now I think the two things are orthogonal.
You need something like MI so that UIs, even text-y ones like Emacs,
can drive gdb intelligently.
But, for folks using the CLI, you need better scripting than what has
historically been provided. I suppose in theory this could be
provided by whatever is driving MI -- but perhaps at the cost of
having to rewrite app-specific gdb scripts once per UI.
Tom
next prev parent reply other threads:[~2008-04-15 23:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 7:55 Lokesh Kumar
2008-04-11 10:52 ` Vladimir Prus
2008-04-11 14:31 ` Marc Khouzam
2008-04-11 12:19 ` André Pönitz
2008-04-12 22:46 ` Gordon Prieur
2008-04-14 2:18 ` Lokesh Kumar
2008-04-14 13:32 ` Nick Roberts
2008-04-16 8:10 ` Doug Evans
2008-04-16 9:47 ` Tom Tromey [this message]
2008-04-16 15:20 ` Daniel Jacobowitz
2008-04-14 13:43 ` Bob Rossi
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=m3iqyivfwu.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
/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