Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andreas Schwab <schwab@suse.de>
Cc: jjaimon@yahoo.com, gdb@sourceware.org
Subject: Re: pthread_sigmask and gdb
Date: Mon, 06 Nov 2006 14:16:00 -0000	[thread overview]
Message-ID: <20061106141641.GA30933@nevyn.them.org> (raw)
In-Reply-To: <jek6287jsx.fsf@sykes.suse.de>

On Mon, Nov 06, 2006 at 03:04:46PM +0100, Andreas Schwab wrote:
> Jaimon Jose <jjaimon@Yahoo.com> writes:
> 
> > Still, SIGINT is passed to the program being debugged instead of GDB
> > handling this.  I have attached a sample program where I can reproduce
> > this. I tried this on Solaris and HPUX.  Once I attach to the running
> > program, I can interrupt the program using "Ctrl-C".  But, this doesn't
> > work on gdb ( on SLES, SuSE 10.1 and RHAS 3.0 - gdb 6.4 and 6.0 ) and
> > the signal is delivered to the running program.  Any help is appreciated.
> 
> Looks like a kernel bug.  Since gdb does not receive any notification of
> the signal it cannot do anything about that.

Yes.  To be more specific, the problem is not pthread_sigmask but
sigwaitinfo / rt_sigsuspend.  I thought some recent kernel changes
(TIF_RESTORE_SIGMASK) would have improved this, and in fact I can't see
how it still happens, but it does still seem to happen.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-11-06 14:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 13:55 Jaimon Jose
2006-11-06 14:05 ` Andreas Schwab
2006-11-06 14:16   ` Daniel Jacobowitz [this message]
2006-11-06 14:18   ` Jaimon Jose
2006-11-06 14:35     ` 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=20061106141641.GA30933@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=jjaimon@yahoo.com \
    --cc=schwab@suse.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