From owner-freebsd-threads@FreeBSD.ORG Tue Oct 9 06:50:52 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FD6C16A418; Tue, 9 Oct 2007 06:50:52 +0000 (UTC) (envelope-from girish_hilage@persistent.co.in) Received: from bmapps.persistent.co.in (outgoing.persistent.co.in [202.54.11.87]) by mx1.freebsd.org (Postfix) with ESMTP id 7993C13C43E; Tue, 9 Oct 2007 06:50:51 +0000 (UTC) (envelope-from girish_hilage@persistent.co.in) Received: from bmapps.persistent.co.in (unknown [127.0.0.1]) by bmapps.persistent.co.in (Symantec Mail Security) with ESMTP id 2E32E528F79; Tue, 9 Oct 2007 12:20:50 +0530 (IST) X-AuditID: 0a4e0006-a5bd7bb0000061f3-4c-470b24ca82e4 Received: from mail.persistent.co.in (unknown [10.78.0.1]) by bmapps.persistent.co.in (Symantec Mail Security) with ESMTP id 014E04E4002; Tue, 9 Oct 2007 12:20:50 +0530 (IST) Received: from ps2408.persistent.co.in ([10.77.196.113]) by mail.persistent.co.in (MOS 3.8.5-GA) with ESMTP id BMW36663 (AUTH girish_hilage); Tue, 9 Oct 2007 12:20:49 +0530 (IST) From: Girish Hilage To: Kip Macy In-Reply-To: References: <1191824849.2054.5.camel@ps2408.persistent.co.in> <1191911671.2054.32.camel@ps2408.persistent.co.in> Date: Tue, 09 Oct 2007 12:21:12 +0530 Message-Id: <1191912673.2054.41.camel@ps2408.persistent.co.in> Mime-Version: 1.0 X-Mailer: Evolution 2.6.0 (2.6.0-1) X-Junkmail-Whitelist: YES (by domain whitelist at mail6.persistent.co.in) X-Brightmail-Tracker: AAAAAA== Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Daniel Eischen , freebsd-threads@freebsd.org Subject: Re: Co-opting signals X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2007 06:50:52 -0000 Thanks Kip. My application is using pthread_kill() to send SIGUSR1 to child threads. I am using 4.x and I want to make sure if SIGUSR1 is not being co-opted. Or for a complete information what all signals are being co-opted and how should I find out from libc_r source that it's not being co-opted? I grep'ed for SIGUSR1 in libc_r source code and did not find it being used anywhere so I came to the conclusion that it's not being co-opted. Is greping through the source code enough to determine that the signal is not being used? On Mon, 2007-10-08 at 23:36 -0700, Kip Macy wrote: > libc_r has been disconnected from the build for some time. > > On 10/8/07, Girish Hilage wrote: > > Thanks Daniel for your response. > > But I want to know if libc_r is still(in it's latest version) co-opting > > signals internally? > > > > Regards, > > Girish > > > > On Mon, 2007-10-08 at 15:01 -0400, Daniel Eischen wrote: > > > > > On Mon, 8 Oct 2007, Girish Hilage wrote: > > > > > > > Hi, > > > > > > > > I heard that, user level pthreads co-opt some signals to get their > > > > job done. > > > > Can anybody please let me know which are these signals? > > > > > > Not true since 4.x since only libc_r did this. Since FreeBSD 5.x, > > > the default thread libraries (libpthread/libkse, and libthr) do > > > not use signals for their implementation. Under 5.x and subsequent, > > > just compile and link your program normally (use -pthread or > > > -lpthread when linking) and you will get the default thread > > > library (not libc_r, which has been deprecated in 7.x/current). > > > > > _______________________________________________ > > freebsd-threads@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" > >