From owner-freebsd-threads@FreeBSD.ORG Thu Oct 6 23:20:21 2005 Return-Path: X-Original-To: freebsd-threads@hub.freebsd.org Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BA6416A41F for ; Thu, 6 Oct 2005 23:20:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18C9843D45 for ; Thu, 6 Oct 2005 23:20:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j96NKKwW047189 for ; Thu, 6 Oct 2005 23:20:20 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j96NKKcr047188; Thu, 6 Oct 2005 23:20:20 GMT (envelope-from gnats) Date: Thu, 6 Oct 2005 23:20:20 GMT Message-Id: <200510062320.j96NKKcr047188@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: Daniel Eischen Cc: Subject: Re: threads/84778: libpthread busy loop/hang with Java when handling signals and Runtime.exec X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2005 23:20:21 -0000 The following reply was made to PR threads/84778; it has been noted by GNATS. From: Daniel Eischen To: freebsd@spatula.net Cc: bug-followup@freebsd.org Subject: Re: threads/84778: libpthread busy loop/hang with Java when handling signals and Runtime.exec Date: Thu, 6 Oct 2005 19:11:38 -0400 (EDT) On Thu, 6 Oct 2005 freebsd@spatula.net wrote: > Some of us do not have the luxury of running -current and an alpha-quality > port on production servers. > > This is a legitimate bug affecting jdk 1.4 on freebsd-stable, even if it > does belong in -java and not -threads. > > Would it not be better to actually find the cause of the problem and make > sure a fix got committed back to the stable branch/port for the majority > of FreeBSD Java users? I didn't close the bug (if it is a bug). I only have time and resources to track and run -current. And since it works on -current, and the thread libraries are the same between -current and -stable, I can only assume there is nothing to backport anyways, at least with regard to libpthread (the library). Obviously the kernels vary somewhat. -- DE