Date: Tue, 9 Oct 2007 00:05:40 -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: <b1fa29170710090005j314e2686q560603045c58fd70@mail.gmail.com> In-Reply-To: <1191912673.2054.41.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> <b1fa29170710082336w2637ce32w2cb769388db0d748@mail.gmail.com> <1191912673.2054.41.camel@ps2408.persistent.co.in>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/8/07, Girish Hilage <girish_hilage@persistent.co.in> wrote: > > 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? Linuxthreads used SIGUSR1. libc_r uses SIGVTALRM for driving preemptive context switches. > > > 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 <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" > > > > > > DISCLAIMER ========== This e-mail may contain privileged and confidential > information which is the property of Persistent Systems Ltd. It is intended > only for the use of the individual or entity to which it is addressed. If > you are not the intended recipient, you are not authorized to read, retain, > copy, print, distribute or use this message. If you have received this > communication in error, please notify the sender and delete all copies of > this message. Persistent Systems Ltd. does not accept any liability for > virus infected mails. =========== "Persistent Systems Pvt. Ltd. is now > PERSISTENT SYSTEMS LIMITED" ===========
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b1fa29170710090005j314e2686q560603045c58fd70>