From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: GDB does not respond to CTRL+Z and CTRL+C
Date: Tue, 20 Jun 2006 18:19:00 -0000 [thread overview]
Message-ID: <20060620180453.GA30199@nevyn.them.org> (raw)
In-Reply-To: <200606202002.05813.bartoschek@or.uni-bonn.de>
On Tue, Jun 20, 2006 at 08:02:05PM +0200, Christoph Bartoschek wrote:
> Am Dienstag 20 Juni 2006 19:03 schrieb Daniel Jacobowitz:
>
> > It works for me; does it work for you if you debug a simple process (I
> > usually use /bin/cat when I want something I can attach to)?
>
> It works when I attach to cat or tail -f but not when I attach to our
> programm.
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.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-20 18:04 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 [this message]
2006-06-20 18:31 ` Christoph Bartoschek
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=20060620180453.GA30199@nevyn.them.org \
--to=drow@false.org \
--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