From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-41920-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 29358 invoked by alias); 9 Dec 2005 20:52:14 -0000
Received: (qmail 29347 invoked by uid 22791); 9 Dec 2005 20:52:13 -0000
X-Spam-Check-By: sourceware.org
Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17)     by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Fri, 09 Dec 2005 20:52:12 +0000
Received: from drow by nevyn.them.org with local (Exim 4.54) 	id 1EkpDu-0005XF-LZ; Fri, 09 Dec 2005 15:52:10 -0500
Date: Sat, 10 Dec 2005 02:10:00 -0000
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [linux] Always ignore restart/cancellation signals
Message-ID: <20051209205210.GA21244@nevyn.them.org>
Mail-Followup-To: Mark Kettenis <mark.kettenis@xs4all.nl>, 	gdb-patches@sourceware.org
References: <200512081950.jB8Jo9im029464@elgar.sibelius.xs4all.nl> <20051208133824.24b4c680@ironwood.lan> <20051208204301.GA29490@nevyn.them.org> <uzmnajxuh.fsf@gnu.org> <20051209143451.GA11917@nevyn.them.org> <ulkyujpof.fsf@gnu.org> <20051209144651.GA12425@nevyn.them.org> <uhd9ije8k.fsf@gnu.org> <20051209185810.GA18701@nevyn.them.org> <200512092049.jB9Kn59V026226@elgar.sibelius.xs4all.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200512092049.jB9Kn59V026226@elgar.sibelius.xs4all.nl>
User-Agent: Mutt/1.5.8i
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2005-12/txt/msg00183.txt.bz2

On Fri, Dec 09, 2005 at 09:49:05PM +0100, Mark Kettenis wrote:
> Ah yes, it all comes back to me.  Believe SIGRTMIN will be 32, unless
> you link your stuff with libpthreads, since that consumes two signals
> for internal use, and therefore SIGRTMIN will be 34.  Are the signal

Nowadays I believe they are always reserved; it's valid to dlopen
libpthread.so.

> numbers hardcoded in libpthread (in particular the NPTL one) or does
> it depend on whether there are other consumers of real-time signals?

They're hardcoded.

-- 
Daniel Jacobowitz
CodeSourcery, LLC