From owner-freebsd-bugs  Tue Aug 10  8:20: 7 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id 2FCC31544D
	for <freebsd-bugs@FreeBSD.org>; Tue, 10 Aug 1999 08:20:05 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id IAA93560;
	Tue, 10 Aug 1999 08:20:02 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Date: Tue, 10 Aug 1999 08:20:02 -0700 (PDT)
Message-Id: <199908101520.IAA93560@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: jin@george.lbl.gov
Subject: Re: bin/13008: kill fails in libc_r
Reply-To: jin@george.lbl.gov
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR bin/13008; it has been noted by GNATS.

From: jin@george.lbl.gov
To: FreeBSD-gnats-submit@FreeBSD.ORG, mark@tgsoft.com
Cc:  
Subject: Re: bin/13008: kill fails in libc_r
Date: Tue, 10 Aug 1999 08:12:59 -0700 (PDT)

 } >How-To-Repeat:
 } 
 }    Sorry, no sample code. I have hacked up the application to the
 }    point that it is no longer recognizeable.
 
 This duplicated kern/11984. This simple code is in there.
 
 } >Fix:
 }         
 }    pthread_kill probably needs to know how to kill processes that
 }    are waiting for file locks.
 
 The problem is that libc_r does not provide a flag to tell thread
 kernel if any thread is being killing, so that if the killed thread
 is in dead loop status or some locked status, then program will hang
 or wait forever.
 
 	-Jin
 
 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message