From: Daniel Jacobowitz <drow@false.org>
To: Andy Howell <AndyHowell@raitechnology.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB is not trapping SIGINT
Date: Mon, 03 Apr 2006 13:21:00 -0000 [thread overview]
Message-ID: <20060403132125.GA5007@nevyn.them.org> (raw)
In-Reply-To: <4430AB93.4050004@raitechnology.com>
On Sun, Apr 02, 2006 at 11:58:59PM -0500, Andy Howell wrote:
> Hello,
>
> I'm having problems getting GDB to not pass SIGINT to my program. In my
> main thread I do a sigwait for SIGINT. When I'm debugging, I don't want
> this called. "info handle" shows that SIGINT should not be being passed
> to my app.
>
> I using GDB 6.3 on RH Linux.
But how are you using it? :-) An example, please.
You also did not mention what kernel version you are using; at least
one sigwait-related kernel bug has been reported. And it looks like
it is still present in current 2.6 kernels, so you may want to report
this to the kernel developers. sys_rt_sigtimedwait calls
dequeue_signal, but never lets ptrace see it. Maybe the bits from
get_signal_to_deliver can be moved into dequeue_signal now.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-03 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 4:59 Andy Howell
2006-04-03 13:21 ` Daniel Jacobowitz [this message]
2006-04-04 5:33 ` Andy Howell
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=20060403132125.GA5007@nevyn.them.org \
--to=drow@false.org \
--cc=AndyHowell@raitechnology.com \
--cc=gdb@sources.redhat.com \
/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