From: Daniel Jacobowitz <drow@false.org>
To: Fred Fish <fnf@specifix.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFC] Patch for QUIT macro support
Date: Fri, 13 Oct 2006 13:30:00 -0000 [thread overview]
Message-ID: <20061013133046.GA9478@nevyn.them.org> (raw)
In-Reply-To: <200610130622.39164.fnf@specifix.com>
On Fri, Oct 13, 2006 at 06:22:39AM -0700, Fred Fish wrote:
> On Friday 13 October 2006 05:43, Fred Fish wrote:
> > To test a possible fix for this, I made the following change:
>
> OK, guess I should keep up with the gdb-patches list more, particularly
> before posting. :-)
>
> I see Nick Roberts just posted a patch a few hours earlier that
> addresses the issue of where quit_flag is set. It also occured to
> me after posting my quick and dirty patch that it probably wasn't
> necessary to jump all the way back into the event loop signal
> handling code, just simply continue to check for the quit_flag
> and call quit when it's set.
Do you mean the big async patch? If so it's still worth fixing this in
isolation. Otherwise, I must have missed a patch.
I may not have time to look at this for a while - I find the event loop
so confusing - but in the meantime, it's come up before:
http://sourceware.org/ml/gdb-patches/2003-08/msg00213.html
http://sourceware.org/ml/gdb-patches/2004-02/msg00530.html
http://sourceware.org/ml/gdb-patches/2004-05/msg00234.html
Maybe one of those threads will be enlightening on how it's "supposed"
to work.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-13 13:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 12:43 Fred Fish
2006-10-13 13:22 ` Fred Fish
2006-10-13 13:30 ` Daniel Jacobowitz [this message]
2006-10-13 13:49 ` Fred Fish
2007-01-21 17:44 ` Daniel Jacobowitz
2007-01-21 19:23 ` Fred Fish
[not found] ` <200610151800.k9FI0fDS016688@elgar.sibelius.xs4all.nl>
2007-01-22 14:41 ` Fred Fish
2007-02-08 14:34 ` Daniel Jacobowitz
2007-02-08 20:49 ` Nick Roberts
2007-02-08 21:17 ` Fred Fish
2007-02-08 21:51 ` Nick Roberts
2006-10-13 14:58 ` Fred Fish
2007-02-08 14:34 ` Daniel Jacobowitz
2006-10-16 0:08 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=20061013133046.GA9478@nevyn.them.org \
--to=drow@false.org \
--cc=fnf@specifix.com \
--cc=gdb-patches@sources.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