From owner-freebsd-emulation  Wed Sep  6  9:59:38 2000
Delivered-To: freebsd-emulation@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP id 9095B37B422
	for <freebsd-emulation@FreeBSD.ORG>; Wed,  6 Sep 2000 09:59:34 -0700 (PDT)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id MAA15617;
	Wed, 6 Sep 2000 12:48:12 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e86GmCd25472;
	Wed, 6 Sep 2000 12:48:12 -0400 (EDT)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed,  6 Sep 2000 12:48:11 -0400 (EDT)
To: nate@yogotech.com (Nate Williams)
Cc: marcel@cup.hp.com, freebsd-emulation@FreeBSD.ORG
Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support
In-Reply-To: <200009060447.WAA23183@nomad.yogotech.com>
References: <14773.43466.744621.411519@grasshopper.cs.duke.edu>
	<200009060447.WAA23183@nomad.yogotech.com>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14774.29608.353021.688597@grasshopper.cs.duke.edu>
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Nate Williams writes:
 > > Currently the IBM jdk & jvm don't run under our linux abi.  This had
 > > previously been attributed to the "sigaltstack: Cannot allocate
 > > memory" message one sees when running it.  Upon further investigation,
 > > this appears to be a red herring.
 > 
 > Umm, I'd believe this except that someone sent me a patch (which I've
 > forwarded to Marcel) that fixes this and is related to the sigalstack
 > error above.  At least the author of the patch claims that the IBM JDK
 > now runs successfully on his box, running some version of FreeBSD. :)

Perhaps he's using a different version of the IBM java stuff?  I'm
using the "IBMJava2-SDK-13.tgz" that I downloaded last week.  On a
linux box, (where I can actually get version info) :

java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20000815 (JIT enabled: jitc))


The change you're referring to isn't all that much different that what 
I'd been doing previously (setting MINSIGSTKSZ to 2048 in sys/signal.h).

I tried the change, and it doesn't seem to help at all.

 > > The "real" problem is as simple
 > > (or, rather, complex) as the fact that we don't support SA_SIGINFO
 > > style signal handlers under the linux abi.
 > 
 > [ Great explanation deleted ]
 > 
 > Hmm, I'm at a loss.  I've heard that things work fine with the
 > signalstack issues fixed, so maybe the java program that he is running
 > doesn't tickle the bug, although I find that rather difficult to believe
 > given that almost every Java program known to man is multi-threaded.

Maybe IBM moved to using SA_SIGINFO handlers for their thread
coordination?

Drew


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