This is the mail archive of the
mailing list for the GDB project.
Re: pthread_sigmask and gdb
- From: Daniel Jacobowitz <drow at false dot org>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: jjaimon at yahoo dot com, gdb at sourceware dot org
- Date: Mon, 6 Nov 2006 09:16:41 -0500
- Subject: Re: pthread_sigmask and gdb
- References: <454F3EB5.7010700@Yahoo.com> <firstname.lastname@example.org>
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.