From: Daniel Jacobowitz <drow@false.org>
To: Sascha Radike <sascha@pasalacqua.de>
Cc: gdb@sourceware.org
Subject: Re: Unable to interrupt a stepping GDB
Date: Tue, 20 Mar 2007 13:55:00 -0000 [thread overview]
Message-ID: <20070320135527.GA31823@caradoc.them.org> (raw)
In-Reply-To: <000001c76af2$f9828960$02b2a8c0@insanenotebook>
On Tue, Mar 20, 2007 at 02:23:38PM +0100, Sascha Radike wrote:
> Should I raise a bug ? Does anyone know how to fix this?
Not offhand, but I agree that it should be fixed. Our way of
handling user Control-C is very complicated, though.
There's a "QUIT;" in resume() already. It looks like that's supposed
to accomplish what you want, but we're not setting the flag it checks
in time. I guess the question is which of the various SIGINT handlers
is running for you.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-20 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 13:23 Sascha Radike
2007-03-20 13:55 ` Daniel Jacobowitz [this message]
[not found] ` <000001c76b15$3a2c3750$02b2a8c0@insanenotebook>
[not found] ` <20070320173306.GA10566@caradoc.them.org>
2007-03-21 8:00 ` Sascha Radike
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=20070320135527.GA31823@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=sascha@pasalacqua.de \
/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