From: Christoph Bartoschek <bartoschek@or.uni-bonn.de>
To: gdb@sourceware.org
Subject: Re: GDB does not respond to CTRL+Z and CTRL+C
Date: Tue, 20 Jun 2006 18:31:00 -0000 [thread overview]
Message-ID: <200606202018.56169.bartoschek@or.uni-bonn.de> (raw)
In-Reply-To: <20060620180453.GA30199@nevyn.them.org>
> Then it is likely that your program is blocking the signal. GDB
> doesn't handle either directly; it forwards them to the program and
> lets the OS handle delivery.
I do not think that we block the signal. However, I have to check the code.
But this does not explain why I am able to use CTRL+Z and CTRL+C as intended
after sending SIGSTOP directly to GDB and foregrounding it again.
CTRL+Z and CTRL+C are only ignored until GDB receives the first SIGSTOP via
the kill command. If the signals are blocked, then I would expect that GDB
behaves similarly before and after SIGSTOP.
If the signals are really blocked, how should one interrupt debugging to set
breakpoints for example?
Christoph Bartoschek
next prev parent reply other threads:[~2006-06-20 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 17:03 Christoph Bartoschek
2006-06-20 17:59 ` Daniel Jacobowitz
2006-06-20 18:04 ` Christoph Bartoschek
2006-06-20 18:19 ` Daniel Jacobowitz
2006-06-20 18:31 ` Christoph Bartoschek [this message]
2006-06-20 20:08 ` 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=200606202018.56169.bartoschek@or.uni-bonn.de \
--to=bartoschek@or.uni-bonn.de \
--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