Date: Wed, 11 Nov 1998 13:04:10 -0500 (EST) From: Brian Feldman <green@unixhelp.org> To: "Richard Seaman, Jr." <lists@tar.com> Cc: "current@freebsd.org" <current@FreeBSD.ORG> Subject: Re: RFSIGSHARE ready? Message-ID: <Pine.BSF.4.05.9811111302240.24080-100000@janus.syracuse.net> In-Reply-To: <199811111754.LAA21780@ns.tar.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 11 Nov 1998, Richard Seaman, Jr. wrote: > ==================BEGIN FORWARDED MESSAGE================== > >From: "Richard Seaman, Jr." <lists@tar.com> > >To: "Brian Feldman" <green@unixhelp.org> > >Cc: "current@freebsd." <current@freebsd> > >Date: Wed, 11 Nov 98 11:51:43 -0600 > >Reply-To: "Richard Seaman, Jr." <lists@tar.com> > >Subject: Re: RFSIGSHARE ready? > > > > On Wed, 11 Nov 1998 12:23:46 -0500 (EST), Brian Feldman wrote: > > >In some programs, the program > >getsto spinning in pthread_handle_create and CANNOT be killed, for some > >reason or another. In other cases, tsleep (invoked from sigsuspend) is > >sleeping forever, of course wakeup works but it's still in a while() loop > >so it just continues. In this manner, both situations are unkillable, no > >matter WHAT signal is sent (I sent all of them to test by the way) > > I found a similar problem when I first invoked a threaded program > using linux threads. The problem went away when I moved > THREAD_STACK_START_ADDRESS down to 0xe0000000. Creating an unkillable process? this is _NOT_ a good thing. And should not be able to be accomplished under any circumstances. Tho, I can think of now, ttywait (I believe) is one such. Cheers, Brian Feldman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9811111302240.24080-100000>