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: Wed, 27 Feb 2008 22:56:00 -0000 [thread overview]
Message-ID: <20080227225435.GA30252@caradoc.them.org> (raw)
In-Reply-To: <47C5E7E8.4000309@st.com>
On Wed, Feb 27, 2008 at 10:44:56PM +0000, Antony KING wrote:
> The signal handler is the restored default handler, "handle_sigint". My
> target interface only substitutes that default SIGINT handler when
> implementing the target_wait() functionality (it is modelled on remote.c).
>
> My first thought was that QUIT should achieve the effect I need but
> quit_flag, as was pointed out, is not being set soon enough. Also,
> forcing an immediate_quit is not suitable since I would like to stop the
> stepping cleanly with a target SIGINT (plus it breaks my target
> interface, but that is my problem :-).
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.
I'm not sure why you'd want to use a target SIGINT for this case.
If we're between steps, we should just make sure we don't send
another step. I suppose I hadn't thought about the case between
stepping and waiting...
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-02-27 22:55 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 [this message]
2008-02-29 22:09 ` Antony KING
2008-02-29 22:49 ` Daniel Jacobowitz
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=20080227225435.GA30252@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