From: Daniel Jacobowitz <drow@false.org>
To: Antony KING <antony.king@st.com>
Cc: gdb@sourceware.org
Subject: Re: Any solution to not being able to interrupt step in GDB ?
Date: Fri, 29 Feb 2008 22:49:00 -0000 [thread overview]
Message-ID: <20080229222450.GA21398@caradoc.them.org> (raw)
In-Reply-To: <47C881B8.30401@st.com>
On Fri, Feb 29, 2008 at 10:05:44PM +0000, Antony KING wrote:
> Daniel Jacobowitz wrote:
>> Why doesn't quit_flag get set? That's how I think we ought to do
>> this. Avoid immediate_quit, that's dangerous to mess with.
>
> In my grep'ing of the (6.6) sources, I could only find quit_flag being
> set when async_request_quit() is called, by the event processing loop. It
> is also set in request_quit() but this API does not seem to be used.
Are you working on 6.6 rather than HEAD? Fred Fish moved quit_flag
setting from async_request_quit to handle_sigint on 2007-02-09, which
is later than your sources. That should simplify things a bit!
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-02-29 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 22:12 Antony KING
2008-02-27 22:45 ` Daniel Jacobowitz
2008-02-27 22:46 ` Antony KING
2008-02-27 22:56 ` Daniel Jacobowitz
2008-02-29 22:09 ` Antony KING
2008-02-29 22:49 ` Daniel Jacobowitz [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=20080229222450.GA21398@caradoc.them.org \
--to=drow@false.org \
--cc=antony.king@st.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