From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-41917-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 17008 invoked by alias); 9 Dec 2005 19:36:22 -0000
Received: (qmail 16995 invoked by uid 22791); 9 Dec 2005 19:36:22 -0000
X-Spam-Check-By: sourceware.org
Received: from gandalf.inter.net.il (HELO gandalf.inter.net.il) (192.114.186.17)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 09 Dec 2005 19:36:20 +0000
Received: from nitzan.inter.net.il (nitzan.inter.net.il [192.114.186.20]) 	by gandalf.inter.net.il (MOS 3.7.1-GA) 	with ESMTP id HFI03937; 	Fri, 9 Dec 2005 21:35:57 +0200 (IST)
Received: from HOME-C4E4A596F7 (IGLD-80-230-152-80.inter.net.il [80.230.152.80]) 	by nitzan.inter.net.il (MOS 3.7.2-GA) 	with ESMTP id CEM02972 (AUTH halo1); 	Fri, 9 Dec 2005 21:35:55 +0200 (IST)
Date: Sat, 10 Dec 2005 01:29:00 -0000
Message-Id: <uacfajc6a.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
In-reply-to: <20051209185810.GA18701@nevyn.them.org> (message from Daniel 	Jacobowitz on Fri, 9 Dec 2005 13:58:10 -0500)
Subject: Re: [linux] Always ignore restart/cancellation signals
Reply-to: Eli Zaretskii <eliz@gnu.org>
References: <20051208142420.GA21882@nevyn.them.org> <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>
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/msg00180.txt.bz2

> Date: Fri, 9 Dec 2005 13:58:10 -0500
> From: Daniel Jacobowitz <drow@false.org>
> 
> If the thread library is kind enough to tell us which signals it is
> using, then we use those numbers.  If it isn't, we must guess.  The
> only correct guess is __SIGRTMIN (32 on all Linux systems, and this is
> Linux-specific code...) and __SIGRTMIN+1.

So you are saying that we should use __SIGRTMIN if we have no better
way of telling which signals are used, yes?  I agree.