From owner-freebsd-emulation  Thu Sep  7 15:21:30 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 4AA7D37B422
	for <freebsd-emulation@FreeBSD.ORG>; Thu,  7 Sep 2000 15:21:28 -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 SAA20656;
	Thu, 7 Sep 2000 18:13:50 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e87MDoA28085;
	Thu, 7 Sep 2000 18:13:50 -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: Thu,  7 Sep 2000 18:13:50 -0400 (EDT)
To: nate@yogotech.com (Nate Williams)
Cc: Bruce Evans <bde@zeta.org.au>, marcel@cup.hp.com,
	freebsd-emulation@FreeBSD.ORG
Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support
In-Reply-To: <200009072209.QAA06661@nomad.yogotech.com>
References: <200009071533.JAA05353@nomad.yogotech.com>
	<Pine.BSF.4.21.0009080844380.30205-100000@besplex.bde.org>
	<200009072209.QAA06661@nomad.yogotech.com>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14776.4695.816482.749092@grasshopper.cs.duke.edu>
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Nate Williams writes:
 > 
 > And the size is allocated inside the application's space?  I thought the
 > size was allocated inside the kernel, hence the need for the system
 > call.

The system call sets a flag and sets the sigstat stack pointer in the
process struct.  Look at the code for "allocating" space for the
signal handler context in the various sendsig() functions.

 > > Bumping the size in the kernel corresponds to using unallocated space
 > > beyond the end of the space allocated by the application.
 > 
 > So how would you propose fixing this?  In Linux, the minimum size is <<
 > FreeBSD's minimum size.  Either we decrease FreeBSD's minimum size or we
 > abort the request, causing these applications to fail.

I'd suggest reducing FreeBSD's minimum size. 

Drew


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