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:45:00 -0000 [thread overview]
Message-ID: <20080227221218.GA27709@caradoc.them.org> (raw)
In-Reply-To: <47C5DD59.5090608@st.com>
On Wed, Feb 27, 2008 at 09:59:53PM +0000, Antony KING wrote:
> Is there any clean solution I can use which allows me to break out this
> loop if there is a pending SIGINT event waiting to be processed ? There
> seems a be a need for a way to "stop stepping" when Ctrl-C is pressed.
> One thought I have is to fake a target SIGINT signal by checking for a
> pending SIGINT event after returning from target_wait() and modifying
> ecs before calling handle_inferior_event().
I can refer you to the reply to the message you linked; which signal
handler is running when not in your "sweet spot"?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-02-27 22:12 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 [this message]
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
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=20080227221218.GA27709@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