Date: Tue, 09 Oct 2007 12:04:31 +0530 From: Girish Hilage <girish_hilage@persistent.co.in> To: Daniel Eischen <deischen@freebsd.org> Cc: freebsd-threads@freebsd.org Subject: Re: Co-opting signals Message-ID: <1191911671.2054.32.camel@ps2408.persistent.co.in> In-Reply-To: <Pine.GSO.4.64.0710081123560.29684@sea.ntplx.net> References: <1191824849.2054.5.camel@ps2408.persistent.co.in> <Pine.GSO.4.64.0710081123560.29684@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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). >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1191911671.2054.32.camel>