From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH:MI] Event notification
Date: Thu, 01 May 2008 18:57:00 -0000 [thread overview]
Message-ID: <20080501185728.GE22218@caradoc.them.org> (raw)
In-Reply-To: <18439.56134.456709.118980@kahikatea.snap.net.nz>
I don't think anyone responded to this.
On Fri, Apr 18, 2008 at 11:20:38AM +1200, Nick Roberts wrote:
> I've not run the testsuite as I imagine it will break in many places. I want
> to get this idea of decoupling MI output from the input command accepted first.
> In this respect, it is somewhat similar to asynchronous output in asynchronous
> mode.
I'm fine with this idea. The thread changed observer looks fine. I
think that the frame changed observer will fire too often;
select_frame is often used with cleanups to temporarily select another
frame.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-05-01 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 0:42 Nick Roberts
2008-05-01 18:57 ` Daniel Jacobowitz [this message]
2008-06-10 2:20 ` Nick Roberts
2008-06-10 2:54 ` Daniel Jacobowitz
2008-06-10 4:25 ` Nick Roberts
2008-06-10 7:02 ` Pedro Alves
2008-05-04 12:19 ` Vladimir Prus
2008-05-04 21:34 ` Daniel Jacobowitz
2008-05-04 23:19 ` 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=20080501185728.GE22218@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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