From owner-freebsd-java Wed Mar 10 20:22:18 1999 Delivered-To: freebsd-java@freebsd.org Received: from cafe.muraoka.info.waseda.ac.jp (cafe.muraoka.info.waseda.ac.jp [133.9.68.49]) by hub.freebsd.org (Postfix) with ESMTP id 6811A14D70 for ; Wed, 10 Mar 1999 20:22:14 -0800 (PST) (envelope-from shudoh@muraoka.info.waseda.ac.jp) Received: from muraoka.info.waseda.ac.jp (shudoh@localhost [127.0.0.1]) by cafe.muraoka.info.waseda.ac.jp (8.9.1a/3.7W) with ESMTP id NAA03845; Thu, 11 Mar 1999 13:20:50 +0900 Message-Id: <199903110420.NAA03845@cafe.muraoka.info.waseda.ac.jp> To: Nate Williams Cc: freebsd-java@FreeBSD.ORG Subject: Re: jre1.1.7 core dump on FreeBSD 3.1 (intel) In-reply-to: Your message of "Wed, 10 Mar 1999 18:07:06 MST." <199903110107.SAA12226@mt.sri.com> Date: Thu, 11 Mar 1999 13:20:50 +0900 From: SHUDO Kazuyuki Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > When > > I run either java or jre, I get a "Floating point exception" and I get a > > core file. > None that I'm aware of. Are you using a 386 box or something that might > cause floating point exceptions? FreeBSD don't mask some floating point exceptions which are masked on initial state of x87. Overflow(OM), Devided by zero(ZM) and illegal operation(IM) aren't masked. Does JDK for FreeBSD change these FPU exception masks from default value? We can investigate the states of the masks by the following code: #include int main(int argc, char **argv) { unsigned short cw; __asm__("fnstcw %0" : "=m"(cw)); printf("FPU control word: 0x%04x\n", (int)cw); return 0; } The code shows FPU control word. On linux: 0x037f On FreeBSD: 0x1272 Kazuyuki SHUDO Happy Hacking! Muraoka Lab., Grad. School of Sci. & Eng., Waseda Univ. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message