From: Tom Tromey <tromey@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: archer@sourceware.org, jan.kratochvil@redhat.com
Subject: Re: tromey/python non-trivial merge notification
Date: Mon, 14 Oct 2013 14:30:00 -0000 [thread overview]
Message-ID: <87wqlg2add.fsf@fleche.redhat.com> (raw)
In-Reply-To: <525BBB9C.2030006@redhat.com> (Phil Muldoon's message of "Mon, 14 Oct 2013 10:38:36 +0100")
Phil> Then we thought about using current_interp_command_loop instead. This
Phil> would work fine, but it would be MI incompatible. I could not think
Phil> of a reason why gdb.cli() would be invoked from MI. (It does not make
Phil> a whole lot of sense to do so, but someone might prove me wrong ;) )
Yeah.
The intended use for this feature was to be able to start gdb without a
CLI, using "gdb -P"; then later give the user a CLI if "something happened".
There's no reason to do this kind of thing in MI.
Tom
prev parent reply other threads:[~2013-10-14 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 9:38 Phil Muldoon
2013-10-14 14:30 ` Tom Tromey [this message]
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=87wqlg2add.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pmuldoon@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).