From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [MI/RFC] Emit ^running via observer.
Date: Fri, 20 Jun 2008 06:53:00 -0000 [thread overview]
Message-ID: <18523.6804.971901.408892@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200806140108.24047.vladimir@codesourcery.com>
> This patch fixes an issue in MI code that was present since at least 1999.
> We output ^running before even trying to resume the target, not to mention
> making sure the target is resumed. So, if resuming fails, we'd get ^running,
> followed by ^error, and I don't really know if current frontends will like
> it at all.
>
> Now that we have observer for resume, and that observer is called after
> target is resumed, we can emit ^running from that observer. The immediate
> bonus is that ^running is now emitted for every command that resumes the
> inferior, even for CLI commands. Another (unexpected) bonus, is that since
^^^^^^^^^^^^^^^^^^^^^
> now ^running and *running is output in a single place, we can produce them
> in consistent order.
I would like to see this patch committed! I've not tested it but I should have
Emacs working with MI shortly and then I can regularly test this and other
changes.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-06-20 2:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 22:01 Vladimir Prus
2008-06-20 6:53 ` Nick Roberts [this message]
2008-06-25 15:04 ` Vladimir Prus
2008-06-26 13:33 ` Nick Roberts
2008-06-26 18:54 ` Vladimir Prus
2008-06-26 19:34 ` Daniel Jacobowitz
2008-06-28 11:34 ` Vladimir Prus
2008-06-28 16:35 ` Vladimir Prus
2008-06-27 6:58 ` Nick Roberts
2008-06-27 11:58 ` Vladimir Prus
2008-06-28 5:49 ` Nick Roberts
2008-06-28 9:41 ` Vladimir Prus
2008-06-28 10:16 ` Nick Roberts
2008-06-28 10:44 ` Vladimir Prus
2008-06-29 2:40 ` Nick Roberts
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=18523.6804.971901.408892@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@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