Date: Mon, 8 Oct 2007 23:36:29 -0700 From: "Kip Macy" <kip.macy@gmail.com> To: "Girish Hilage" <girish_hilage@persistent.co.in> Cc: Daniel Eischen <deischen@freebsd.org>, freebsd-threads@freebsd.org Subject: Re: Co-opting signals Message-ID: <b1fa29170710082336w2637ce32w2cb769388db0d748@mail.gmail.com> In-Reply-To: <1191911671.2054.32.camel@ps2408.persistent.co.in> References: <1191824849.2054.5.camel@ps2408.persistent.co.in> <Pine.GSO.4.64.0710081123560.29684@sea.ntplx.net> <1191911671.2054.32.camel@ps2408.persistent.co.in>
next in thread | previous in thread | raw e-mail | index | archive | help
libc_r has been disconnected from the build for some time. On 10/8/07, Girish Hilage <girish_hilage@persistent.co.in> 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" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b1fa29170710082336w2637ce32w2cb769388db0d748>