From owner-freebsd-java Sun Feb 1 18:36:21 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA17371
for java-outgoing; Sun, 1 Feb 1998 18:36:21 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from sniff.iway.nl (sniff.iway.nl [193.78.30.251])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17366
for <freebsd-java@FreeBSD.ORG>; Sun, 1 Feb 1998 18:36:19 -0800 (PST)
(envelope-from iang@systemics.com)
Received: from hayek.guvnet (noddy [192.168.1.5]) by sniff.iway.nl (8.7.5/8.7.3) with SMTP id FAA08369; Mon, 2 Feb 1998 05:18:19 +0100 (MET)
Message-ID: <34D531C8.2B6B8D8B@systemics.com>
Date: Mon, 02 Feb 1998 02:39:04 +0000
From: Ian Grigg <iang@systemics.com>
Organization: Systemics
X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-971022-SNAP i386)
MIME-Version: 1.0
To: freebsd-java@FreeBSD.ORG
Subject: jdk115 JNI requires ELF, gcc makes a.out
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
Hi Team,
I've been using your FreeBSD JDK 1.1.5, and it hums. I've compiled up
and tested all of the current Cryptix distribution, and it went through
with no problems.
I'm now trying something harder: Cryptix-C Native (JNI). I've got it to
compile ok, with only this change:
cd bin; ln -s i386 i586
which was required for javah.
However, the result that is produced by gcc is a.out format, and the JVM
seems to require ELF.
I guess we are stuck with the JDK requiring ELF?
(I couldn't find any doco on the subject of ELFs, other than a hint that
if I installed a patch kit called Elfkit I could effectively compile for
ELFs. But I couldn't find much recent status on that, it seemed to be
at the development stage.)
Now, I guess this isn't a bug, but I'd be grateful for any pointers...
Is there a way to produce ELFs that I've missed, or a way to use a.out
in the JVM?
Other than that, great job, it's now the distribution JDK for Cryptix.
--
iang systemics.com
FP: 1189 4417 F202 5DBD 5DF3 4FCD 3685 FDDE on pgp.com
From owner-freebsd-java Sun Feb 1 18:43:45 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA18039
for java-outgoing; Sun, 1 Feb 1998 18:43:45 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from cs1.cityscope.net (cs1.cityscope.net [206.222.183.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18024
for <java@freebsd.org>; Sun, 1 Feb 1998 18:43:40 -0800 (PST)
(envelope-from bahwi@cityscope.net)
Received: from cs1.cityscope.net.net (pm1-65.cityscope.net [209.16.48.65]) by cs1.cityscope.net (8.8.8/8.6.9) with SMTP id UAA28865 for <java@freebsd.org>; Sun, 1 Feb 1998 20:47:45 -0600
Message-Id: <199802020247.UAA28865@cs1.cityscope.net>
Comments: Authenticated sender is <bahwi@mail.cityscope.net>
From: "bahwi" <bahwi@cityscope.net>
To: java@FreeBSD.ORG
Date: Sat, 31 Jan 1998 20:39:48 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: I need some help with installing the JDK 1.1.5
Reply-to: bahwi@technologist.com
X-mailer: Pegasus Mail for Win32 (v2.54)
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
I downloaded the (dap? is that is what it is called?)
binary distribution of the JDK 1.1.5 for FreeBSD. Could
someone tell me exactly what to do to get it working
fully(semi-fully?) What would the classpath be and all
that, or is there an installation thing or a port for it?
(So I can do make install) Thanks for putting up with this
Unix - Half-Newbie.. Many thanks.
-bahwi
email- bahwi@technologist.com
ICQ Name: bahwi UIN: 3328936
iChat Name: bahwi
-EOF
From owner-freebsd-java Sun Feb 1 18:54:55 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA19353
for java-outgoing; Sun, 1 Feb 1998 18:54:55 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19347
for <freebsd-java@FreeBSD.ORG>; Sun, 1 Feb 1998 18:54:54 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id TAA11093;
Sun, 1 Feb 1998 19:54:48 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id TAA26197; Sun, 1 Feb 1998 19:54:46 -0700
Date: Sun, 1 Feb 1998 19:54:46 -0700
Message-Id: <199802020254.TAA26197@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Ian Grigg <iang@systemics.com>
Cc: freebsd-java@FreeBSD.ORG
Subject: Re: jdk115 JNI requires ELF, gcc makes a.out
In-Reply-To: <34D531C8.2B6B8D8B@systemics.com>
References: <34D531C8.2B6B8D8B@systemics.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
> I've been using your FreeBSD JDK 1.1.5, and it hums. I've compiled up
> and tested all of the current Cryptix distribution, and it went through
> with no problems.
Cool. There are still some gotchas to track down, but for the most part
it seems to work.
> I'm now trying something harder: Cryptix-C Native (JNI). I've got it to
> compile ok, with only this change:
>
> cd bin; ln -s i386 i586
>
> which was required for javah.
Weird? They are doing something non-portable.
> However, the result that is produced by gcc is a.out format, and the JVM
> seems to require ELF.
Huh? I don't think so. FreeBSD doesn't do ELF, so nothing we've
created requires and/or uses ELF. If the Cryptix-C stuff in JNI, do
they provide you with C sources and/or libraries? If libraries, are
*they* ELF compiled? If so, then they are not for FreeBSD, but for
Solaris and/or Linux, and will not work under FreeBSD. (That's why they
call it Java *NATIVE* Interface, which means it's not portable across
architectures/OS's.)
In short, the current JDK requires everything to be 100% Pure and/or
compiled for FreeBSD in the case of the JNI stuff.
Nate
From owner-freebsd-java Sun Feb 1 18:55:31 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA19437
for java-outgoing; Sun, 1 Feb 1998 18:55:31 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19430
for <java@freebsd.org>; Sun, 1 Feb 1998 18:55:28 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id TAA11101;
Sun, 1 Feb 1998 19:55:28 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id TAA26205; Sun, 1 Feb 1998 19:55:26 -0700
Date: Sun, 1 Feb 1998 19:55:26 -0700
Message-Id: <199802020255.TAA26205@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: bahwi@technologist.com
Cc: java@FreeBSD.ORG
Subject: Re: I need some help with installing the JDK 1.1.5
In-Reply-To: <199802020247.UAA28865@cs1.cityscope.net>
References: <199802020247.UAA28865@cs1.cityscope.net>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
> I downloaded the .. binary distribution of the JDK 1.1.5 for FreeBSD.
Check out http://www.freebsd.org/java
Nate
From owner-freebsd-java Sun Feb 1 19:01:27 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA20358
for java-outgoing; Sun, 1 Feb 1998 19:01:27 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from oznet02.ozemail.com.au (oznet02.ozemail.com.au [203.2.192.124])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20351
for <java@freebsd.org>; Sun, 1 Feb 1998 19:01:25 -0800 (PST)
(envelope-from joe.shevland@horizonti.com)
Received: from jupiter ([203.33.128.245]) by oznet02.ozemail.com.au (8.8.4/8.6.12) with ESMTP id OAA22383; Mon, 2 Feb 1998 14:01:15 +1100 (EST)
Message-Id: <199802020301.OAA22383@oznet02.ozemail.com.au>
From: "Joe Shevland" <joe.shevland@horizonti.com>
To: <bahwi@technologist.com>, <java@FreeBSD.ORG>
Subject: Re: I need some help with installing the JDK 1.1.5
Date: Mon, 2 Feb 1998 13:59:39 +1100
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1162
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
----------
> From: bahwi <bahwi@cityscope.net>
> To: java@freebsd.org
> Subject: I need some help with installing the JDK 1.1.5
> Date: Sunday, 1 February 1998 7:39
>
> I downloaded the (dap? is that is what it is called?)
> binary distribution of the JDK 1.1.5 for FreeBSD. Could
> someone tell me exactly what to do to get it working
> fully(semi-fully?) What would the classpath be and all
> that, or is there an installation thing or a port for it?
> (So I can do make install) Thanks for putting up with this
> Unix - Half-Newbie.. Many thanks.
1) RTFM :-)
2) Sorry if I'm offering bad assistance here, because I haven't installed the 1.1.5 version yet, but here goes anyway (sorry also
for any browser paragraph mangling that occurs).
Install the package file (I guess its a .tar.gz?) to /usr/local/jdk I guess.
Your classpath is the location (path) of the 'classes.zip' file and other class libraries you require. For instance, by installing
to /usr/local/jdk, your classpath would probably be:
setenv CLASSPATH "/usr/local/jdk/lib/classes.zip",
although I could be wrong about the lib subdirectory. Often your CLASSPATH needs to also include the current directory '.', and
maybe other class libraries you've developed (so setenv CLASSPATH ".:$CLASSPATH").
Your PATH envirovariable needs to include the binaries that come with the JDK, so update this. e.g. add /usr/local/jdk/bin to your
path (or I think it may be /usr/local/jdk/i386/bin).
Failing all this, go to 1).
Hope it helps (even with all the inconsistencies with shells etc.) :-)
Joe Shevland
joe.shevland@horizonti.com
From owner-freebsd-java Sun Feb 1 21:20:43 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA05032
for java-outgoing; Sun, 1 Feb 1998 21:20:43 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from inet-user-gw-1.us.oracle.com (inet-user-gw-1.us.oracle.com [192.86.155.82])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05025
for <freebsd-java@freebsd.org>; Sun, 1 Feb 1998 21:20:39 -0800 (PST)
(envelope-from SSANKARA.IN.oracle.com.ofcmail@in.oracle.com)
Received: from dwarpal.in.oracle.com (dwarpal.in.oracle.com [152.69.176.11])
by inet-user-gw-1.us.oracle.com (8.8.5/8.8.5) with SMTP id VAA28020
for <freebsd-java@freebsd.org>; Sun, 1 Feb 1998 21:18:11 -0800 (PST)
Received: by dwarpal.in.oracle.com (8.6.13/37.8)
id AAA08800; Mon, 2 Feb 1998 00:52:32 -0500
Message-Id: <199802020552.AAA08800@dwarpal.in.oracle.com>
Date: 02 Feb 98 08:35:53 +0330
From: "SIVA SANKARAN" <SSANKARA.IN.oracle.com.ofcmail@in.oracle.com>
To: freebsd-java@FreeBSD.ORG
Subject: TimeSlicing in JVM
X-Orcl-Application: Disclaimer What ever I send is my opinion and don't neccessarily represent that of ORACLE Corporation
MIME-Version: 1.0
X-Mailer: Oracle InterOffice (version 4.0.5.1.55)
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
Hi all,
In the standard JDK code, for Solaris Green-threads the 'Timeslicing'
(i.e if more than one thread, runs at the same priority using Round-Robin
method of scheduling) is disabled. Therefore other threads, waiting in the
Runnable Queue of the same priority of the currently running thread has to
wait, till the running thread finishes or yields.
The code is in
src/freebsd/java/green_threads/src/clock.c . The function is timeSlicer. But
the variable
TimeSlice is initialized to 0 (=> no TimeSlice )
Is this the desired behavior. Can I make Round-Robin fashion of
scheduling for
equal priority threads. If so can you suggest some reasonable value for the
TimeSlice.
Is there any other issue involved, in enabling the TimeSlice.
Regards
Shankar.
From owner-freebsd-java Sun Feb 1 22:05:46 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA08739
for java-outgoing; Sun, 1 Feb 1998 22:05:46 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08732
for <freebsd-java@freebsd.org>; Sun, 1 Feb 1998 22:05:45 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA12181;
Sun, 1 Feb 1998 23:05:44 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id XAA26684; Sun, 1 Feb 1998 23:05:41 -0700
Date: Sun, 1 Feb 1998 23:05:41 -0700
Message-Id: <199802020605.XAA26684@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "SIVA SANKARAN" <SSANKARA.IN.oracle.com.ofcmail@in.oracle.com>
Cc: freebsd-java@FreeBSD.ORG
Subject: Re: TimeSlicing in JVM
In-Reply-To: <199802020552.AAA08800@dwarpal.in.oracle.com>
References: <199802020552.AAA08800@dwarpal.in.oracle.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
> In the standard JDK code, for Solaris Green-threads the 'Timeslicing'
> (i.e if more than one thread, runs at the same priority using Round-Robin
> method of scheduling) is disabled.
Yes, that is true (for many reasons).
> Therefore other threads, waiting in the
> Runnable Queue of the same priority of the currently running thread has to
> wait, till the running thread finishes or yields.
Right again.
> The code is in
> src/freebsd/java/green_threads/src/clock.c . The function is timeSlicer. But
> the variable
> TimeSlice is initialized to 0 (=> no TimeSlice )
BTW, this file is an exact copy of the solaris code. (It's a symlink in
the FreeBSD-JDK development tree.)
> Is this the desired behavior. Can I make Round-Robin fashion of
> scheduling for
> equal priority threads.
You can try, but how do you propose 'interrupting' a running thread?
Remember, everything runs in a single process space (w/out kernel
threads), and that if a running thread is in a system call there is no
way to pre-empt it reliably.
Because of this 'feature', I suspect the authors gave up trying to
implement a fair-scheduling algorithm, because it would not
deterministic enough due to the above issue (and other similar to it).
One of the really nasty things in the current green-thread port which
exists on all *nix platforms which don't use kernel threads is that a
single thread can sit in a tight loop and never let go, which means that
if you have one errant thread your entire VM is hosed. This is a *bad*
thing, but I don't see any way around it w/out kernel support.
Nate
From owner-freebsd-java Sun Feb 1 22:28:55 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA10956
for java-outgoing; Sun, 1 Feb 1998 22:28:55 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10950
for <freebsd-java@FreeBSD.ORG>; Sun, 1 Feb 1998 22:28:50 -0800 (PST)
(envelope-from jb@cimlogic.com.au)
Received: (from jb@localhost)
by cimlogic.com.au (8.8.7/8.8.7) id RAA00645;
Mon, 2 Feb 1998 17:33:12 +1100 (EST)
(envelope-from jb)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199802020633.RAA00645@cimlogic.com.au>
Subject: Re: TimeSlicing in JVM
In-Reply-To: <199802020605.XAA26684@mt.sri.com> from Nate Williams at "Feb 1, 98 11:05:41 pm"
To: nate@mt.sri.com (Nate Williams)
Date: Mon, 2 Feb 1998 17:33:12 +1100 (EST)
Cc: SSANKARA.IN.oracle.com.ofcmail@in.oracle.com, freebsd-java@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
Nate Williams wrote:
> One of the really nasty things in the current green-thread port which
> exists on all *nix platforms which don't use kernel threads is that a
> single thread can sit in a tight loop and never let go, which means that
> if you have one errant thread your entire VM is hosed. This is a *bad*
> thing, but I don't see any way around it w/out kernel support.
That's not quite true 8-) in all cases. By leaving a timer running, a
thread running in a tight loop can be interrupted by a SIGVTALRM and the
user-thread kernel can schedule another thread. libc_r does this. So
tight loops or thread-hogs are OK provided that the thread doesn't
hand on to locked resources. It's non-blocking syscalls that end in tears.
Regards,
--
John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
From owner-freebsd-java Sun Feb 1 22:36:54 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA11596
for java-outgoing; Sun, 1 Feb 1998 22:36:54 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11587
for <freebsd-java@FreeBSD.ORG>; Sun, 1 Feb 1998 22:36:51 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA12376;
Sun, 1 Feb 1998 23:36:23 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id XAA26813; Sun, 1 Feb 1998 23:36:21 -0700
Date: Sun, 1 Feb 1998 23:36:21 -0700
Message-Id: <199802020636.XAA26813@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: John Birrell <jb@cimlogic.com.au>
Cc: nate@mt.sri.com (Nate Williams),
SSANKARA.IN.oracle.com.ofcmail@in.oracle.com, freebsd-java@FreeBSD.ORG
Subject: Re: TimeSlicing in JVM
In-Reply-To: <199802020633.RAA00645@cimlogic.com.au>
References: <199802020605.XAA26684@mt.sri.com>
<199802020633.RAA00645@cimlogic.com.au>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
> > One of the really nasty things in the current green-thread port which
> > exists on all *nix platforms which don't use kernel threads is that a
> > single thread can sit in a tight loop and never let go, which means that
> > if you have one errant thread your entire VM is hosed. This is a *bad*
> > thing, but I don't see any way around it w/out kernel support.
>
> That's not quite true 8-) in all cases. By leaving a timer running, a
> thread running in a tight loop can be interrupted by a SIGVTALRM and the
> user-thread kernel can schedule another thread. libc_r does this.
I'm with you so far. :)
> So tight loops or thread-hogs are OK provided that the thread doesn't
> hand on to locked resources.
And here-in lies the rub. Doing this while avoiding races and deadlocks
in 'the hard thing'. But, now that I've given it more than a nano-cycle
in my brain, it's probably not any harder than doing this sort of thing
with kernel threads, since they also get scheduled while holding onto
locks and such, so this problem must already be solved for the most part
inside of the JDK sources.
So, the moral of the story is to listen to John. He knows what he's
talking about!
> It's non-blocking syscalls that end in tears.
*grin*
I also remember thinking seriously about this problem after reading a
Java threads book, and they brought up another point that I can't recall
right now that was also one of those 'syscall' types of problems. If I
remember or find it I'll send something to the list.
Nate
From owner-freebsd-java Sun Feb 1 22:44:00 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA12217
for java-outgoing; Sun, 1 Feb 1998 22:44:00 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA12204
for <freebsd-java@FreeBSD.ORG>; Sun, 1 Feb 1998 22:43:56 -0800 (PST)
(envelope-from jb@cimlogic.com.au)
Received: (from jb@localhost)
by cimlogic.com.au (8.8.7/8.8.7) id RAA00688;
Mon, 2 Feb 1998 17:49:15 +1100 (EST)
(envelope-from jb)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199802020649.RAA00688@cimlogic.com.au>
Subject: Re: TimeSlicing in JVM
In-Reply-To: <199802020636.XAA26813@mt.sri.com> from Nate Williams at "Feb 1, 98 11:36:21 pm"
To: nate@mt.sri.com (Nate Williams)
Date: Mon, 2 Feb 1998 17:49:15 +1100 (EST)
Cc: jb@cimlogic.com.au, nate@mt.sri.com,
SSANKARA.IN.oracle.com.ofcmail@in.oracle.com, freebsd-java@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
Nate Williams wrote:
> I also remember thinking seriously about this problem after reading a
> Java threads book, and they brought up another point that I can't recall
> right now that was also one of those 'syscall' types of problems. If I
> remember or find it I'll send something to the list.
It might be a scheduler issue. Like the one where a lower priority
thread locks a resource that a higher priority thread needs, but the
lower priority thread can't get enough CPU time to finish using the
resource. libc_r deals with this by using an incremental priority
that is reset when a thread gets to run, but is incremented the
longer it is ready to run but prevented from running. Eventually
the lower priority thread has a higher effective priority and gets
to see its name in lights.
Regards,
--
John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
From owner-freebsd-java Mon Feb 2 03:46:26 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA16274
for java-outgoing; Mon, 2 Feb 1998 03:46:26 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from sniff.iway.nl (sniff.iway.nl [193.78.30.251])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16231
for <freebsd-java@FreeBSD.ORG>; Mon, 2 Feb 1998 03:46:02 -0800 (PST)
(envelope-from iang@systemics.com)
Received: from hayek.guvnet (noddy [192.168.1.5]) by sniff.iway.nl (8.7.5/8.7.3) with SMTP id OAA09787; Mon, 2 Feb 1998 14:27:58 +0100 (MET)
Message-ID: <34D5B297.43856914@systemics.com>
Date: Mon, 02 Feb 1998 11:48:39 +0000
From: Ian Grigg <iang@systemics.com>
Organization: Systemics
X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-971022-SNAP i386)
MIME-Version: 1.0
To: Nate Williams <nate@mt.sri.com>
CC: freebsd-java@FreeBSD.ORG
Subject: Re: jdk115 JNI requires ELF, gcc makes a.out
References: <34D531C8.2B6B8D8B@systemics.com> <199802020254.TAA26197@mt.sri.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
Nate Williams wrote:
> > However, the result that is produced by gcc is a.out format, and the JVM
> > seems to require ELF.
>
> Huh? I don't think so. FreeBSD doesn't do ELF, so nothing we've
> created requires and/or uses ELF.
You're absolutely right, of course, I looked more closely and found I
had hooked into the Linux JVM, through some dodgy scripts. It still
doesn't work with the FreeBSD JVM, but I'll have to leave it for now, it
looks like some local problem, and I need to fiddle with PATHS.
Just to complete these questions:
> If the Cryptix-C stuff in JNI, do
> they provide you with C sources and/or libraries?
In this case, I am part of the "they" and and I'm trying to compile the
source for FreeBSD (and Solaris). When I can do that, I plan to start
shipping the source in our main src distribution, as well as a bunch of
pre-compiled dists for platforms. It was written/ported/developed on
W95/NT and needs some re-porting.
> If libraries, are
> *they* ELF compiled? If so, then they are not for FreeBSD, but for
> Solaris and/or Linux, and will not work under FreeBSD.
The libraries I have compiled are a.out format. I fallaciously assumed
that the ELF was a generic thing in the JDK port, and spent all my time
hunting for methods to produce ELF formats.
> In short, the current JDK requires everything to be 100% Pure and/or
> compiled for FreeBSD in the case of the JNI stuff.
That's the confirmation I needed, thanks. No ELFs.
--
iang systemics.com
FP: 1189 4417 F202 5DBD 5DF3 4FCD 3685 FDDE on pgp.com
From owner-freebsd-java Mon Feb 2 08:08:34 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA19047
for java-outgoing; Mon, 2 Feb 1998 08:08:34 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from damon.com (wQZi/WS6MAgkFCp0bC1209Lj2JfWPhdZ@damon.com [207.170.114.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19036
for <freebsd-java@FreeBSD.ORG>; Mon, 2 Feb 1998 08:08:28 -0800 (PST)
(envelope-from dap@damon.com)
Received: (from dap@localhost)
by damon.com (8.8.7/8.8.7) id KAA06305;
Mon, 2 Feb 1998 10:03:25 -0600 (CST)
(envelope-from dap)
From: Damon Permezel <dap@damon.com>
Message-Id: <199802021603.KAA06305@damon.com>
Subject: Re: TimeSlicing in JVM
In-Reply-To: <199802020636.XAA26813@mt.sri.com> from Nate Williams at "Feb 1, 98 11:36:21 pm"
To: nate@mt.sri.com (Nate Williams)
Date: Mon, 2 Feb 1998 10:03:25 -0600 (CST)
Cc: jb@cimlogic.com.au, nate@mt.sri.com,
SSANKARA.IN.oracle.com.ofcmail@in.oracle.com, freebsd-java@FreeBSD.ORG,
java-port@mt.sri.com (Java Port)
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
On a similar thread, what do folks feel about the implementation of
yield? With non-preemptive threads, yield does:
(from sysThreadYield()):
if (runnable_queue && runnable_queue->priority == self->priority) {
... yields to threads only of the same priority.
This means I cannot write a CPU hog function, run it in a low priority
thread, and call yield() periodicially, expecting the higher pri runnables
to get some CPU.
This forces me to run my CPU hog at "normal" priority, and means that
the async garbage collector thread will never run, unless I also arrange to
call it from the CPU hog function.
I would have preferred to have the hog run at THREAD_MIN (or whatever it was
called) which is where the async GC runs, and have it be able to yield
the CPU to the user interface threads, and other threads, as well as the GC.
(I know that this doesn't really solve the GC issue.)
I haven't experimented with changing it to:
if (runnable_queue && runnable_queue->priority >= self->priority) {
as it is often easier (and "better") to work around these issues in my app,
but I believe such a change is warranted.
From owner-freebsd-java Mon Feb 2 08:12:31 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA20104
for java-outgoing; Mon, 2 Feb 1998 08:12:31 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from damon.com (GmkIC8rY3a0zZznPF9HjQ6CRu67rI9EA@damon.com [207.170.114.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20089
for <freebsd-java@FreeBSD.ORG>; Mon, 2 Feb 1998 08:12:14 -0800 (PST)
(envelope-from dap@damon.com)
Received: (from dap@localhost)
by damon.com (8.8.7/8.8.7) id KAA06331;
Mon, 2 Feb 1998 10:11:27 -0600 (CST)
(envelope-from dap)
From: Damon Permezel <dap@damon.com>
Message-Id: <199802021611.KAA06331@damon.com>
Subject: Re: TimeSlicing in JVM
In-Reply-To: <199802020649.RAA00688@cimlogic.com.au> from John Birrell at "Feb 2, 98 05:49:15 pm"
To: jb@cimlogic.com.au (John Birrell)
Date: Mon, 2 Feb 1998 10:11:27 -0600 (CST)
Cc: nate@mt.sri.com, jb@cimlogic.com.au,
SSANKARA.IN.oracle.com.ofcmail@in.oracle.com, freebsd-java@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
"John Birrell sez: "
> Nate Williams wrote:
> > I also remember thinking seriously about this problem after reading a
> > Java threads book, and they brought up another point that I can't recall
> > right now that was also one of those 'syscall' types of problems. If I
> > remember or find it I'll send something to the list.
>
> It might be a scheduler issue. Like the one where a lower priority
> thread locks a resource that a higher priority thread needs, but the
> lower priority thread can't get enough CPU time to finish using the
> resource. libc_r deals with this by using an incremental priority
> that is reset when a thread gets to run, but is incremented the
> longer it is ready to run but prevented from running. Eventually
> the lower priority thread has a higher effective priority and gets
> to see its name in lights.
>
The green_threads scheduler has priority inversion.
Not sure if it works. This is one of the issues of turning on time slicing.
Perhaps there were many good reasons why it is off for green_threads....
I guess one of us should scrutinize the code, see if we really think
turning on the timeslicing will work (at the basic level, without too
much associated hacking) and then turn it on.
If it looks like it works, then we should consider dropping the code into the
official release, initially requiring the setting of a resource or an
environment var to enable timeslice.
I have a basic test for this, and I am motifated, so I volunteer....
From owner-freebsd-java Mon Feb 2 08:23:21 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA21240
for java-outgoing; Mon, 2 Feb 1998 08:23:21 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from damon.com (PLKIivhudH8o74FD3tERc15MXHIx/HYB@damon.com [207.170.114.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21234
for <freebsd-java@freebsd.org>; Mon, 2 Feb 1998 08:23:18 -0800 (PST)
(envelope-from dap@damon.com)
Received: (from dap@localhost)
by damon.com (8.8.7/8.8.7) id KAA06376;
Mon, 2 Feb 1998 10:22:40 -0600 (CST)
(envelope-from dap)
From: Damon Permezel <dap@damon.com>
Message-Id: <199802021622.KAA06376@damon.com>
Subject: Re: TimeSlicing in JVM
In-Reply-To: <199802021611.KAA06331@damon.com> from Damon Permezel at "Feb 2, 98 10:11:27 am"
To: dap@damon.com (Damon Permezel)
Date: Mon, 2 Feb 1998 10:22:40 -0600 (CST)
Cc: jb@cimlogic.com.au, nate@mt.sri.com,
SSANKARA.IN.oracle.com.ofcmail@in.oracle.com, freebsd-java@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
"Damon Permezel sez: "
> "John Birrell sez: "
> > Nate Williams wrote:
> > > I also remember thinking seriously about this problem after reading a
> > > Java threads book, and they brought up another point that I can't recall
> > > right now that was also one of those 'syscall' types of problems. If I
> > > remember or find it I'll send something to the list.
> >
> > It might be a scheduler issue. Like the one where a lower priority
> > thread locks a resource that a higher priority thread needs, but the
> > lower priority thread can't get enough CPU time to finish using the
> > resource. libc_r deals with this by using an incremental priority
> > that is reset when a thread gets to run, but is incremented the
> > longer it is ready to run but prevented from running. Eventually
> > the lower priority thread has a higher effective priority and gets
> > to see its name in lights.
> >
>
> The green_threads scheduler has priority inversion.
> Not sure if it works. This is one of the issues of turning on time slicing.
> Perhaps there were many good reasons why it is off for green_threads....
>
> I guess one of us should scrutinize the code, see if we really think
> turning on the timeslicing will work (at the basic level, without too
> much associated hacking) and then turn it on.
Silly me!
You can just use:
java -ts100 ....
to turn on time slicing with green threads.
>From an initial sniff, I see that there is not a timeslicer thread running.
Where is that FM?
From owner-freebsd-java Mon Feb 2 08:24:12 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA21316
for java-outgoing; Mon, 2 Feb 1998 08:24:12 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from damon.com (Ye+lbBk/UWk4Nx+zkntMViVOcOL56ERs@damon.com [207.170.114.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21311
for <freebsd-java@freebsd.org>; Mon, 2 Feb 1998 08:24:10 -0800 (PST)
(envelope-from dap@damon.com)
Received: (from dap@localhost)
by damon.com (8.8.7/8.8.7) id KAA06394;
Mon, 2 Feb 1998 10:23:52 -0600 (CST)
(envelope-from dap)
From: Damon Permezel <dap@damon.com>
Message-Id: <199802021623.KAA06394@damon.com>
Subject: Re: TimeSlicing in JVM
In-Reply-To: <199802021622.KAA06376@damon.com> from Damon Permezel at "Feb 2, 98 10:22:40 am"
To: dap@fubar.damon.com (Damon Permezel)
Date: Mon, 2 Feb 1998 10:23:52 -0600 (CST)
Cc: dap@damon.com, jb@cimlogic.com.au, nate@mt.sri.com,
SSANKARA.IN.oracle.com.ofcmail@in.oracle.com, freebsd-java@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
"Damon Permezel sez: "
> "Damon Permezel sez: "
> > "John Birrell sez: "
> > > Nate Williams wrote:
> > > > I also remember thinking seriously about this problem after reading a
> > > > Java threads book, and they brought up another point that I can't recall
> > > > right now that was also one of those 'syscall' types of problems. If I
> > > > remember or find it I'll send something to the list.
> > >
> > > It might be a scheduler issue. Like the one where a lower priority
> > > thread locks a resource that a higher priority thread needs, but the
> > > lower priority thread can't get enough CPU time to finish using the
> > > resource. libc_r deals with this by using an incremental priority
> > > that is reset when a thread gets to run, but is incremented the
> > > longer it is ready to run but prevented from running. Eventually
> > > the lower priority thread has a higher effective priority and gets
> > > to see its name in lights.
> > >
> >
> > The green_threads scheduler has priority inversion.
> > Not sure if it works. This is one of the issues of turning on time slicing.
> > Perhaps there were many good reasons why it is off for green_threads....
> >
> > I guess one of us should scrutinize the code, see if we really think
> > turning on the timeslicing will work (at the basic level, without too
> > much associated hacking) and then turn it on.
>
> Silly me!
> You can just use:
>
> java -ts100 ....
>
> to turn on time slicing with green threads.
> From an initial sniff, I see that there is not a timeslicer thread running.
>
I think you mean "now", rather than not, no?
> Where is that FM?
>
Beats me.
From owner-freebsd-java Mon Feb 2 09:51:39 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA00752
for java-outgoing; Mon, 2 Feb 1998 09:51:39 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA00742
for <freebsd-java@FreeBSD.ORG>; Mon, 2 Feb 1998 09:51:35 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA16183;
Mon, 2 Feb 1998 10:51:32 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id KAA28000; Mon, 2 Feb 1998 10:51:30 -0700
Date: Mon, 2 Feb 1998 10:51:30 -0700
Message-Id: <199802021751.KAA28000@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Ian Grigg <iang@systemics.com>
Cc: Nate Williams <nate@mt.sri.com>, freebsd-java@FreeBSD.ORG
Subject: Re: jdk115 JNI requires ELF, gcc makes a.out
In-Reply-To: <34D5B297.43856914@systemics.com>
References: <34D531C8.2B6B8D8B@systemics.com>
<199802020254.TAA26197@mt.sri.com>
<34D5B297.43856914@systemics.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
> > > However, the result that is produced by gcc is a.out format, and the JVM
> > > seems to require ELF.
> >
> > Huh? I don't think so. FreeBSD doesn't do ELF, so nothing we've
> > created requires and/or uses ELF.
>
> You're absolutely right, of course, I looked more closely and found I
> had hooked into the Linux JVM, through some dodgy scripts. It still
> doesn't work with the FreeBSD JVM, but I'll have to leave it for now, it
> looks like some local problem, and I need to fiddle with PATHS.
*phew*. OK, when you've got things working, can you let the list know?
JNI is probably one of the least tested features of the JDK, and it
would nice to know that it works. :) :)
Nate
From owner-freebsd-java Mon Feb 2 09:58:44 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA01519
for java-outgoing; Mon, 2 Feb 1998 09:58:44 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from damon.com (ycqsERAYZ4f6eC/MQvK+a8xq9HTDmoHf@damon.com [207.170.114.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01508
for <freebsd-java@freebsd.org>; Mon, 2 Feb 1998 09:58:36 -0800 (PST)
(envelope-from dap@damon.com)
Received: (from dap@localhost)
by damon.com (8.8.7/8.8.7) id LAA06618;
Mon, 2 Feb 1998 11:54:09 -0600 (CST)
(envelope-from dap)
From: Damon Permezel <dap@damon.com>
Message-Id: <199802021754.LAA06618@damon.com>
Subject: Re: TimeSlicing in JVM
In-Reply-To: <199802021623.KAA06394@damon.com> from Damon Permezel at "Feb 2, 98 10:23:52 am"
To: dap@damon.com (Damon Permezel)
Date: Mon, 2 Feb 1998 11:54:09 -0600 (CST)
Cc: dap@damon.com, jb@cimlogic.com.au, nate@mt.sri.com,
SSANKARA.IN.oracle.com.ofcmail@in.oracle.com, freebsd-java@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
"Damon Permezel sez: "
> "Damon Permezel sez: "
> > "Damon Permezel sez: "
> > > "John Birrell sez: "
> > > > Nate Williams wrote:
> > > > > I also remember thinking seriously about this problem after reading a
> > > > > Java threads book, and they brought up another point that I can't recall
> > > > > right now that was also one of those 'syscall' types of problems. If I
> > > > > remember or find it I'll send something to the list.
> > > >
> > > > It might be a scheduler issue. Like the one where a lower priority
> > > > thread locks a resource that a higher priority thread needs, but the
> > > > lower priority thread can't get enough CPU time to finish using the
> > > > resource. libc_r deals with this by using an incremental priority
> > > > that is reset when a thread gets to run, but is incremented the
> > > > longer it is ready to run but prevented from running. Eventually
> > > > the lower priority thread has a higher effective priority and gets
> > > > to see its name in lights.
> > > >
> > >
> > > The green_threads scheduler has priority inversion.
> > > Not sure if it works. This is one of the issues of turning on time slicing.
> > > Perhaps there were many good reasons why it is off for green_threads....
> > >
> > > I guess one of us should scrutinize the code, see if we really think
> > > turning on the timeslicing will work (at the basic level, without too
> > > much associated hacking) and then turn it on.
> >
> > Silly me!
> > You can just use:
> >
> > java -ts100 ....
> >
> > to turn on time slicing with green threads.
> > From an initial sniff, I see that there is not a timeslicer thread running.
> >
> I think you mean "now", rather than not, no?
>
Correct, but I have observed applications which used to work stop.
For example, using the current non-fractal hallucinations, patched to not call
yield:
LD_LIBRARY_PATH=lib java -ts100 damon.dap.NFH.NFH -w 128
never displays the initial window, and the idle thread is running.
If I change it to `-ts3000' to give it a chance to get the initial window
up, it runs OK, but what use is a 3 second time slice?
Thus, there are bugs which turning timeslice on aggravates.
The sun/awt code has all these locks which think they are not recursively
obtainable, but which are clearly recursive. This may be at least one source
of these problems.
From owner-freebsd-java Mon Feb 2 10:00:39 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA01861
for java-outgoing; Mon, 2 Feb 1998 10:00:39 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from damon.com (PSzla8lklrjk2B37j7jLlVUmr0oHjZKx@damon.com [207.170.114.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01856
for <freebsd-java@freebsd.org>; Mon, 2 Feb 1998 10:00:37 -0800 (PST)
(envelope-from dap@damon.com)
Received: (from dap@localhost)
by damon.com (8.8.7/8.8.7) id MAA06670;
Mon, 2 Feb 1998 12:00:13 -0600 (CST)
(envelope-from dap)
From: Damon Permezel <dap@damon.com>
Message-Id: <199802021800.MAA06670@damon.com>
Subject: Re: TimeSlicing in JVM
In-Reply-To: <199802021754.LAA06618@damon.com> from Damon Permezel at "Feb 2, 98 11:54:09 am"
To: dap@fubar.damon.com (Damon Permezel)
Date: Mon, 2 Feb 1998 12:00:13 -0600 (CST)
Cc: dap@damon.com, jb@cimlogic.com.au, nate@mt.sri.com,
SSANKARA.IN.oracle.com.ofcmail@in.oracle.com, freebsd-java@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
"Damon Permezel sez: "
> "Damon Permezel sez: "
> > "Damon Permezel sez: "
... blah blah blah...
> > >
> > I think you mean "now", rather than not, no?
> >
>
> Correct, but I have observed applications which used to work stop.
> For example, using the current non-fractal hallucinations, patched to not call
> yield:
>
> LD_LIBRARY_PATH=lib java -ts100 damon.dap.NFH.NFH -w 128
>
> never displays the initial window, and the idle thread is running.
> If I change it to `-ts3000' to give it a chance to get the initial window
> up, it runs OK, but what use is a 3 second time slice?
>
> Thus, there are bugs which turning timeslice on aggravates.
> The sun/awt code has all these locks which think they are not recursively
> obtainable, but which are clearly recursive. This may be at least one source
> of these problems.
>
Running with the tiny toolkit, it appears to work "better" in some respects.
tiny toolkit comes with a whole slew of its own problems, though, which I
am somewhat interested in persuing.
export JAVA_AWT_TOOLKIT=sun.awt.tiny.TinyToolkit; LD_LIBRARY_PATH=lib java -ts100 damon.dap.NFH.NFH -w 128
From owner-freebsd-java Mon Feb 2 10:02:13 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA02248
for java-outgoing; Mon, 2 Feb 1998 10:02:13 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from damon.com (AMAF0bZcRaxvFc+QDt9mk8bAYlbVSwA0@damon.com [207.170.114.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02229
for <freebsd-java@freebsd.org>; Mon, 2 Feb 1998 10:02:09 -0800 (PST)
(envelope-from dap@damon.com)
Received: (from dap@localhost)
by damon.com (8.8.7/8.8.7) id MAA06681;
Mon, 2 Feb 1998 12:01:59 -0600 (CST)
(envelope-from dap)
From: Damon Permezel <dap@damon.com>
Message-Id: <199802021801.MAA06681@damon.com>
Subject: Re: jdk115 JNI requires ELF, gcc makes a.out
In-Reply-To: <199802021751.KAA28000@mt.sri.com> from Nate Williams at "Feb 2, 98 10:51:30 am"
To: nate@mt.sri.com (Nate Williams)
Date: Mon, 2 Feb 1998 12:01:59 -0600 (CST)
Cc: iang@systemics.com, nate@mt.sri.com, freebsd-java@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
"Nate Williams sez: "
> > > > However, the result that is produced by gcc is a.out format, and the JVM
> > > > seems to require ELF.
> > >
> > > Huh? I don't think so. FreeBSD doesn't do ELF, so nothing we've
> > > created requires and/or uses ELF.
> >
> > You're absolutely right, of course, I looked more closely and found I
> > had hooked into the Linux JVM, through some dodgy scripts. It still
> > doesn't work with the FreeBSD JVM, but I'll have to leave it for now, it
> > looks like some local problem, and I need to fiddle with PATHS.
>
> *phew*. OK, when you've got things working, can you let the list know?
> JNI is probably one of the least tested features of the JDK, and it
> would nice to know that it works. :) :)
JNI works.... it was one of the first bugs I ran into.
I am certainly interested in any counter examples.
From owner-freebsd-java Mon Feb 2 10:13:54 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA04193
for java-outgoing; Mon, 2 Feb 1998 10:13:54 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04174
for <freebsd-java@freebsd.org>; Mon, 2 Feb 1998 10:13:52 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA16341;
Mon, 2 Feb 1998 11:05:11 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id LAA28174; Mon, 2 Feb 1998 11:05:08 -0700
Date: Mon, 2 Feb 1998 11:05:08 -0700
Message-Id: <199802021805.LAA28174@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Damon Permezel <dap@damon.com>
Cc: nate@mt.sri.com (Nate Williams), iang@systemics.com,
freebsd-java@FreeBSD.ORG
Subject: Re: jdk115 JNI requires ELF, gcc makes a.out
In-Reply-To: <199802021801.MAA06681@damon.com>
References: <199802021751.KAA28000@mt.sri.com>
<199802021801.MAA06681@damon.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
> > *phew*. OK, when you've got things working, can you let the list know?
> > JNI is probably one of the least tested features of the JDK, and it
> > would nice to know that it works. :) :)
>
> JNI works.... it was one of the first bugs I ran into.
>
> I am certainly interested in any counter examples.
I stand corrected. I wasn't aware that it had been tested.
Nate
From owner-freebsd-java Mon Feb 2 10:13:54 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA04200
for java-outgoing; Mon, 2 Feb 1998 10:13:54 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04184
for <freebsd-java@freebsd.org>; Mon, 2 Feb 1998 10:13:52 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA16204;
Mon, 2 Feb 1998 10:54:13 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id KAA28021; Mon, 2 Feb 1998 10:54:09 -0700
Date: Mon, 2 Feb 1998 10:54:09 -0700
Message-Id: <199802021754.KAA28021@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Damon Permezel <dap@damon.com>
Cc: dap@fubar.damon.com (Damon Permezel), jb@cimlogic.com.au, nate@mt.sri.com,
SSANKARA.IN.oracle.com.ofcmail@in.oracle.com, freebsd-java@FreeBSD.ORG
Subject: Re: TimeSlicing in JVM
In-Reply-To: <199802021623.KAA06394@damon.com>
References: <199802021622.KAA06376@damon.com>
<199802021623.KAA06394@damon.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
Damon Permezel writes:
[ Timeslicing discussions ]
There's only comment I'd like to make Re: changing the slice scheduler.
If we do this, we also need a way to kick this in, and leave the
'old/standard/default' behavior the default, so that people don't end up
with different behaviors depending on what OS they are running under.
This is *very* important for me at work, and I suspect many others.
But, it would also be a great thing for debugging and FreeBSD-only
programs to have the usefulness of a better scheduler.
Nate
From owner-freebsd-java Mon Feb 2 10:15:36 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA04429
for java-outgoing; Mon, 2 Feb 1998 10:15:36 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from teel.info-noire.com (XP11-1-3-05.interlinx.qc.ca [207.253.79.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04405
for <freebsd-java@FreeBSD.ORG>; Mon, 2 Feb 1998 10:15:28 -0800 (PST)
(envelope-from alex@gel.usherb.ca)
Received: from localhost (alex@localhost)
by teel.info-noire.com (8.8.8/8.8.8) with SMTP id NAA18563;
Mon, 2 Feb 1998 13:17:42 -0500 (EST)
(envelope-from alex@teel.info-noire.com)
Date: Mon, 2 Feb 1998 13:17:42 -0500 (EST)
From: Alex Boisvert <alex@gel.usherb.ca>
Reply-To: boia01@gel.usherb.ca
To: Damon Permezel <dap@damon.com>
cc: freebsd-java@FreeBSD.ORG
Subject: Re: TimeSlicing in JVM
In-Reply-To: <199802021800.MAA06670@damon.com>
Message-ID: <Pine.BSF.3.95q.980202131421.17812B-101000@teel.info-noire.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-1478741780-886443462=:17812"
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.
--0-1478741780-886443462=:17812
Content-Type: TEXT/PLAIN; charset=US-ASCII
I've been experimenting with timeslices (within the JVM) for a while.
I'd say it works OK since I can't attribute any bug directly to
timeslicing as of now.
Attached to this message are a few .java files to test threads. You can
experiment with these & timeslicing...
Regards,
Alex.
I
--0-1478741780-886443462=:17812
Content-Type: APPLICATION/octet-stream; name="threads.tgz"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.BSF.3.95q.980202131742.17812C@teel.info-noire.com>
Content-Description:
H4sIAO8M1jQAA+1ae2/byBHPv9KnmAq4AxXZtKiXgfjS4lCnqK+4SxAbvRSG
IdDkSlqHIlVyZcdX+Lt3Znb5kijZaev4CuwAsUju7uzs7OxvHptT4YcXixT/
ujf+rf/qOcjr9yejEbwC8I7HXvWXyRtNxgCT4fHAG43GwxF+GXje8BX0n0Wa
DVpnyk8BXvmR+LKv32Pt/6d09LoNr+G0bgX4ib6er/y7OAMfFDfB3UIGC/gs
oygDqTIRzQ7Aj0NsFjGkYiV8JcLoHoKFCD5noBJikgkBcoZ9fJXzWfgZhFKE
LrYfQbsdRH6WVWSYXohM6UcQX5SIwwz0a/tf7dZqfR3JAG4TGUK6jp1uu4Vf
W+f3mRJLN1krd5XKWEWx0yE+ZuQb+DGSt+JPbzrQkxk/O93uCQ5UC5m5mUpW
Dr0+tB/abTPFplyV2dFoVC7E0pexc65w0jn46Ty7vDIiNa9ILWhWlBCCZI1/
30KfPrAk+BKLu2ZVOEZalwxW6TfckUg4+K1YEnz/veH7A3j9LpAcLf7Q69GI
Rj39jCt4o4eRfnR36JygrK5v1NaD6jQ8e0ul93qCljGeLBJi5eB57+sODxD4
Klg4Z7ESabpeoX28+xKIlZJJDMJIt0ck5geyHO12DOM2/SM9zsCprHf/ChXZ
gzFCNkDNTUSZ2D/w17++f//hvJMbyEsf2v8hncvlKhI/JTJ+Mfwf9L0h4v/I
G0zGg/HxgPF/MrH4/y1I4/+GFRj8v6gclxtsg2QlUp/PLr74cCvw/Gc8FO78
e4bzHM1LjlXsa7dyPKdp3MiP5+4WtjYOdQgwGQ7+7kcGX4+ODEDwuY4TBTxy
KWJCijYDhOFJo+983Oq5mF5enbS/yo2cE+ASuhsORicaPLQci+RwsV4SIptJ
DJIjh0s0/6sc8uXBjRk0S1JHvu2fgPwBO+BPr8fohd/BuaGGG91wYxoK1peO
7N10vyO2OAs+l2KESSxYSpL2PlmnoORSuK67Y2Wn3F+i49mxtFSodRo3+sVy
mx73i5dX7BlzHTfaRuH9mve/n4vUuEPFEPQZKPKqs+Usd4ykMby1e5RAbg5/
2FkhSzoK2v2SF2IHB80eTopuPq5p7opfg3DN8YPmfQA0pT9n30MBizDT7VkE
WjwA7Sc7NTKH1/Dp0yc8FncltwO4Xiu9VjIMZJLRmdW7+9JQZOkFSJ8cRrhn
CwAey/+8yajw/6N+n/z/cNK3/v9bUNX/l1ZgAoA/p5TSgbpLGJg1LGac8zGu
Uua3RNh55yME6lYaxvF4BrM0WUIf00AMzPsHwGhFGIeoA4JGhHIuFfiUTMI8
EZkJIBq8DEv2dDcDVT/DY2uOxqs5ms12x2Ow3TV4sH/wQIOvGlTTNOVV3hhr
txa3O+cFWnebo4dpUOSL/CrDE2raIQrHG6HxudiXgoWQBWg1hD9GZ5xRgsMz
UUaVp5DG7aC/KtwOssQk0eSNIDPyVDROZ2j0pFNO8pK1/Pqlbd5SSef3cbAg
o3m+9O/R/G847jP+D8ejyXjC9b/+2LP4/y0oR6LcDKbvr28IcAg85ok6U1PC
s1pznirpZoNHFJsymCBCYGZjymH4sievekddOcClfie1hC2jGdMklr9hcMyM
/eCfa5kKp0z+fmWsyhIMZDGNoSoOlxalKnHMyPgHFLIIxU04r18wq5IGpRmo
nhDPt3ZXrfJaIy7JVMSCdZpiPpqX8FyVaNU43R5zabXwBHTgLvksOKvW4lSj
/rLWZcpdTWvSWu8YHb2BSp+T/OXtW+j09HOZTuh3DdRb/L0n8Pf28N+/oamI
hJ8VG/rI1Kb3U6culnZ4eNJ+XHEN3OuKg42VteJEydn9lkcvDoopa7S2C9i1
wwTRxgEzlrLRyegoouMW1U/KZgXD1ITTdZl8RlO3OD0n5kOh/WKrthfx1Ijr
tjjkNaHzSKkOHrmlUcxQ1kIgL4YMylqICTzqmqnUCTZ1FpmqdK1E/mBjjn10
ro/lM3r/R/3/aDQca/9/fDwcDSeUEY5t/vdt6OiojZ60agVt/ek0Yc+qa6sJ
XeAJSG5FuqAziO8lnnNFGLPAM5XRwIWfhpT0mcMqKN9bYcpHWeNc4C/MhIgo
OqBjT/eCNCpnfYBfkvV84ZIYVTxKk1Nf+SY0QdiRYTY1eVCgg5S8fFz2dnRr
ntvQkEpdNlBclg04hgkUu4lUZCJP01p7g5FAZNmUG+qJFk1yKcMrdqlbqZYZ
FydfPRIlW0cqK7zlFnyCxk/WRlFNbghSHNnzupy4UYzBc151m1yKVkVtuv2T
GWZFRIgc6ztYvwooivUZfFzHsX8dicI96v3Tik+ub/KdlmHDTldz3qbBB2DU
bMygYIqC5s9cnw+nZYq8071SIOFQ1+9g0KXQQF86mngzd7uVWdy6rYTT2p3j
4+MKW9EjtVrrNRK9aFJe1U2v/DX6d743EYGRvlrKrt3ZYhd4DcXN7QOUpe3y
qmbHNe6+GvdFWXrmiejcmyul7WvdB233X3eboM847pzXz29ZeOXnuKL8o7E5
PPkXl1cGAvS3HAWK81SzINyHarBhUCVQeRCzI8jHg/MhlUkq1b1juvz846fp
h49n7z+eXfxj923EXySnTclsVhTbLj3XpTt5upC/YsjEt3yB+I02N8EA06gQ
odRU7fwoynHb8NqItBDyapEWa0fW1eNU1l49Z5k+V+b/AZiRjes++6W6bh07
azlxsZi1LWm1uyUreZchnTbsAT+TIG6J2q2iOVdR5ZLubxJVIpZPmkyXqyoT
aPCtfcrnfOpO5tvout4TdvJ3s1VGkEAdYsIl/8gSHR52ATX6CyZBgWAbSwV6
cMzAkzQU6X+wcQ279l9PbGqOW3vIy0Kfw5ejGJOYRzy54gum331bqLRkyZIl
S5YsWbJkyZIlS5YsWbJkyZIlS5YsWbJkyZIlS5YsWbJkyZIlS5Ys/Y7p35uO
eFAAUAAA
--0-1478741780-886443462=:17812--
From owner-freebsd-java Mon Feb 2 18:29:27 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA04913
for java-outgoing; Mon, 2 Feb 1998 18:29:27 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04883
for <freebsd-java@FreeBSD.ORG>; Mon, 2 Feb 1998 18:29:24 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id SAA01356; Mon, 2 Feb 1998 18:28:50 -0800 (PST)
Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3)
id sma001354; Mon Feb 2 18:28:41 1998
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id SAA13283; Mon, 2 Feb 1998 18:28:35 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199802030228.SAA13283@bubba.whistle.com>
Subject: Re: jdk115 JNI requires ELF, gcc makes a.out
In-Reply-To: <199802021751.KAA28000@mt.sri.com> from Nate Williams at "Feb 2, 98 10:51:30 am"
To: nate@mt.sri.com (Nate Williams)
Date: Mon, 2 Feb 1998 18:28:35 -0800 (PST)
Cc: iang@systemics.com, freebsd-java@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
Nate Williams writes:
> *phew*. OK, when you've got things working, can you let the list know?
> JNI is probably one of the least tested features of the JDK, and it
> would nice to know that it works. :) :)
It works for me too.. in a simple test that does the equivalent
of "ifconfig -a".
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
From owner-freebsd-java Mon Feb 2 19:03:14 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA10010
for java-outgoing; Mon, 2 Feb 1998 19:03:14 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from aiai.ed.ac.uk (eigg.aiai.ed.ac.uk [129.215.41.7])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10005
for <freebsd-java@FreeBSD.ORG>; Mon, 2 Feb 1998 19:03:10 -0800 (PST)
(envelope-from jeff@aiai.ed.ac.uk)
Received: from gairsay.aiai.ed.ac.uk (gairsay.aiai.ed.ac.uk [129.215.105.57])
by aiai.ed.ac.uk (8.8.7/8.8.7) with ESMTP id DAA17245
for <freebsd-java@FreeBSD.ORG>; Tue, 3 Feb 1998 03:03:06 GMT
Received: (jeff@localhost) by gairsay.aiai.ed.ac.uk (8.6.13/8.6.12) id DAA26466 for freebsd-java@FreeBSD.ORG; Tue, 3 Feb 1998 03:03:06 GMT
Date: Tue, 3 Feb 1998 03:03:06 GMT
Message-Id: <199802030303.DAA26466@gairsay.aiai.ed.ac.uk>
From: Jeff Dalton <jeff@aiai.ed.ac.uk>
Subject: ScrollPane segmentation violation
To: freebsd-java@FreeBSD.ORG
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
I'm having trouble using FreeBSD jdk115b2 because an application
that works fine on Suns (and, for that matter, Macs) dies with a
SIGSEGV 11* segmentation violation
in a way that seems connected with ScrollPanes. The evidence is
(a) stack traces that contain lines like this:
java.awt.ScrollPane.getVScrollbarWidth(ScrollPane.java:207)
java.awt.ScrollPane.calculateChildSize(ScrollPane.java:319)
java.awt.ScrollPane.layout(ScrollPane.java:349)
java.awt.ScrollPane.doLayout(ScrollPane.java:305)
java.awt.Container.validateTree(Container.java:529)
java.awt.Container.validateTree(Container.java:536)
java.awt.Container.validate(Container.java:511)
java.awt.Window.pack(Window.java:125)
and (b) that the problem goes away if the ScrollPanes are replaced
by mere Panels.
Before I spend a lot more time trying to figure this out, or
work around it, I wanted to asked whether anyone has seen a
similar problme before and could say what might be going on
and what might be done about it.
-- jeff
From owner-freebsd-java Mon Feb 2 19:28:53 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA13944
for java-outgoing; Mon, 2 Feb 1998 19:28:53 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13927
for <freebsd-java@freebsd.org>; Mon, 2 Feb 1998 19:28:51 -0800 (PST)
(envelope-from hasty@rah.star-gate.com)
Received: from rah (localhost.star-gate.com [127.0.0.1])
by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id TAA04120;
Mon, 2 Feb 1998 19:28:36 -0800 (PST)
(envelope-from hasty@rah.star-gate.com)
Message-Id: <199802030328.TAA04120@rah.star-gate.com>
X-Mailer: exmh version 2.0gamma 1/27/96
To: Jeff Dalton <jeff@aiai.ed.ac.uk>
cc: freebsd-java@FreeBSD.ORG
Subject: Re: ScrollPane segmentation violation
In-reply-to: Your message of "Tue, 03 Feb 1998 03:03:06 GMT."
<199802030303.DAA26466@gairsay.aiai.ed.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Feb 1998 19:28:36 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
The jdk has not crashed over here in a while -- whats different
on my setup is that I compile java with Motif and I am running
current.
If its okay with you just mail me or post the code which
causes the sig fault and I will be happy to track it down.
Cheers,
Amancio
From owner-freebsd-java Mon Feb 2 20:25:50 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA19965
for java-outgoing; Mon, 2 Feb 1998 20:25:50 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19940
for <freebsd-java@FreeBSD.ORG>; Mon, 2 Feb 1998 20:25:48 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA20245;
Mon, 2 Feb 1998 21:25:47 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id VAA00665; Mon, 2 Feb 1998 21:25:46 -0700
Date: Mon, 2 Feb 1998 21:25:46 -0700
Message-Id: <199802030425.VAA00665@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Jeff Dalton <jeff@aiai.ed.ac.uk>
Cc: freebsd-java@FreeBSD.ORG
Subject: Re: ScrollPane segmentation violation
In-Reply-To: <199802030303.DAA26466@gairsay.aiai.ed.ac.uk>
References: <199802030303.DAA26466@gairsay.aiai.ed.ac.uk>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
> I'm having trouble using FreeBSD jdk115b2 because an application
> that works fine on Suns (and, for that matter, Macs) dies with a
>
> SIGSEGV 11* segmentation violation
...
Try out ftp://hub.freebsd.org/pub/java/jdk1.1.5.tar.gz. Many of these
sorts of bugs were fixed by linking in a *real* Motif library.
Nate
ps. I had hoped to roll a new 'GAMMA' release this last weekend, but due
to some recently posted about bugs I decided to wait. However, it
appears that these bugs are no fixed, so I'll try and get something
built this evening and out later tonight.
From owner-freebsd-java Mon Feb 2 20:49:12 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA22170
for java-outgoing; Mon, 2 Feb 1998 20:49:12 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22137
for <freebsd-java@FreeBSD.ORG>; Mon, 2 Feb 1998 20:49:10 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA20401;
Mon, 2 Feb 1998 21:49:08 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id VAA00719; Mon, 2 Feb 1998 21:49:07 -0700
Date: Mon, 2 Feb 1998 21:49:07 -0700
Message-Id: <199802030449.VAA00719@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Archie Cobbs <archie@whistle.com>
Cc: nate@mt.sri.com (Nate Williams), freebsd-java@FreeBSD.ORG
Subject: Re: jdk115 JNI requires ELF, gcc makes a.out
In-Reply-To: <199802030228.SAA13283@bubba.whistle.com>
References: <199802021751.KAA28000@mt.sri.com>
<199802030228.SAA13283@bubba.whistle.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
> Nate Williams writes:
> > *phew*. OK, when you've got things working, can you let the list know?
> > JNI is probably one of the least tested features of the JDK, and it
> > would nice to know that it works. :) :)
>
> It works for me too.. in a simple test that does the equivalent
> of "ifconfig -a".
Cool. I have no easy way of testing it, so it's nice to know someone
is. :)
Nate
From owner-freebsd-java Mon Feb 2 20:53:39 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA22581
for java-outgoing; Mon, 2 Feb 1998 20:53:39 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from sniff.iway.nl (sniff.iway.nl [193.78.30.251])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22574
for <freebsd-java@freebsd.org>; Mon, 2 Feb 1998 20:53:37 -0800 (PST)
(envelope-from iang@systemics.com)
Received: from hayek.guvnet (noddy [192.168.1.5]) by sniff.iway.nl (8.7.5/8.7.3) with SMTP id HAA12520; Tue, 3 Feb 1998 07:35:56 +0100 (MET)
Message-ID: <34D6A37E.29B3C1AE@systemics.com>
Date: Tue, 03 Feb 1998 04:56:30 +0000
From: Ian Grigg <iang@systemics.com>
Organization: Systemics
X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-971022-SNAP i386)
MIME-Version: 1.0
To: freebsd-java@FreeBSD.ORG
Subject: Re: jdk115 JNI requires ELF, gcc makes a.out
References: <199802021801.MAA06681@damon.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
Damon Permezel wrote:
> I am certainly interested in any counter examples.
I'll try :-) I'm back on it now, and I've written a test class which
has the benefit of only involving 400 odd lines of Java code (Cryptix
will soon rival the JDK :-). I'm now seeing useful debugging, and I get
this:
cannot stat
"/usr/local/apps/java/java/bin/../lib/i386/green_threads//home/iang/src/helplets/current/native/build/x86-freebsd/libBlowfish.so"
: No such file or directory
(/home/iang/src/helplets/current/native/build/x86-freebsd/libBlowfish.so)
java.lang.UnsatisfiedLinkError:
/home/iang/src/helplets/current/native/build/x86-freebsd/libBlowfish.so
...
from code which effectively does this:
System.load("/home/iang/src/helplets/current/native/build/x86-freebsd/libBlowfish.so");
(sorry about the long names...).
It is insisting on turning the absolute pathname into one relative to
/usr/local/apps/java/java/bin/../lib/i386/green_threads/
Now, I can fix this by setting LD_LIBRARYPATH to the current dir and
using a relative path:
$ LD_LIBRARY_PATH=$PWD java Blowfish.BlowfishNative
build/x86-freebsd/libBlowfish.so
BlowNat: load: build/x86-freebsd/libBlowfish.so
BlowNat: lib loaded successfully.
BlowNat: Loaded.
BlowNat: FAILED: java.lang.UnsatisfiedLinkError: getLibMajorVersion
Which gets us nicely up to (my) next bug. However, that is the relative
case, not the absolute case, the absolute still fails:
$ LD_LIBRARY_PATH=$PWD java Blowfish.BlowfishNative
$PWD/build/x86-freebsd/libBlowfish.so
BlowNat: load:
/home/iang/src/helplets/current/native/build/x86-freebsd/libBlowfish.so
cannot stat
"/home/iang/src/helplets/current/native//home/iang/src/helplets/current/native/build/x86-freebsd/libBlowfish.so"
: No such file or directory
(/home/iang/src/helplets/current/native/build/x86-freebsd/libBlowfish.so)
java.lang.UnsatisfiedLinkError:
/home/iang/src/helplets/current/native/build/x86-freebsd/libBlowfish.so
...
It's now using the LD_LIBRARYPATH as the root.
The doco for System.load implies only "complete" pathnames should be
used:
===========8<=========
load
public synchronized void load(String filename)
Loads the specified filename as a dynamic library. The filename
argument must be a complete pathname. From java_g it will
automagically insert "_g" before the ".so" (for example
Runtime.getRuntime().load("/home/avh/lib/libX11.so");).
===========8<=========
Perhaps I'd better throw some questions in:
* is "complete" synonymous with absolute?
* is this a bug, or a misinterpretation?
* should I be using System.loadLibrary?
* can I use absolute, relative, or what?
* ...
Note that at this stage I can survive, as a relative solution is fine.
But I'd like to know what the end verdict is, for the doco.
Thanks for your patience.
--
iang systemics.com
FP: 1189 4417 F202 5DBD 5DF3 4FCD 3685 FDDE on pgp.com
From owner-freebsd-java Mon Feb 2 21:55:43 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA28483
for java-outgoing; Mon, 2 Feb 1998 21:55:43 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28478
for <freebsd-java@FreeBSD.ORG>; Mon, 2 Feb 1998 21:55:42 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA20721;
Mon, 2 Feb 1998 22:55:41 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id WAA00791; Mon, 2 Feb 1998 22:55:39 -0700
Date: Mon, 2 Feb 1998 22:55:39 -0700
Message-Id: <199802030555.WAA00791@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Ian Grigg <iang@systemics.com>
Cc: freebsd-java@FreeBSD.ORG
Subject: Re: jdk115 JNI requires ELF, gcc makes a.out
In-Reply-To: <34D6A37E.29B3C1AE@systemics.com>
References: <199802021801.MAA06681@damon.com>
<34D6A37E.29B3C1AE@systemics.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
> will soon rival the JDK :-). I'm now seeing useful debugging, and I get
> this:
>
> cannot stat
> "/usr/local/apps/java/java/bin/../lib/i386/green_threads//home/iang/src/helplets/current/native/build/x86-freebsd/libBlowfish.so"
> : No such file or directory
> (/home/iang/src/helplets/current/native/build/x86-freebsd/libBlowfish.so)
> java.lang.UnsatisfiedLinkError:
> /home/iang/src/helplets/current/native/build/x86-freebsd/libBlowfish.so
> ...
Hmm, I have an idea what might be causing this, but my *very simple*
test code appears to work fine loading libraries:
public class Lib {
public static void main(String args[]) {
new Lib();
}
static {
try {
System.load("/usr/lib/libz.so.2.0");
System.out.println("Library loaded...");
} catch (Exception e) {
System.err.println("Error:" + e);
}
}
}
> System.load("/home/iang/src/helplets/current/native/build/x86-freebsd/libBlowfish.so");
>
> (sorry about the long names...).
No problem.
> It is insisting on turning the absolute pathname into one relative to
> /usr/local/apps/java/java/bin/../lib/i386/green_threads/
I have an idea what might be causing that, but I wouldn't think it would
be doing that in the Java code.
> Now, I can fix this by setting LD_LIBRARYPATH to the current dir and
> using a relative path:
>
> $ LD_LIBRARY_PATH=$PWD java Blowfish.BlowfishNative
> build/x86-freebsd/libBlowfish.so
>
> BlowNat: load: build/x86-freebsd/libBlowfish.so
> BlowNat: lib loaded successfully.
> BlowNat: Loaded.
> BlowNat: FAILED: java.lang.UnsatisfiedLinkError: getLibMajorVersion
>
> Which gets us nicely up to (my) next bug.
I'm assuming the UnsatisfiedLinkErro is yours and not ours, right?
> However, that is the relative
> case, not the absolute case, the absolute still fails:
As above, right.
> Perhaps I'd better throw some questions in:
>
> * is "complete" synonymous with absolute?
Totally qualified, and not relative. (Absolute works too.)
> * is this a bug, or a misinterpretation?
Possibly the former.
> * should I be using System.loadLibrary?
No.
> * can I use absolute, relative, or what?
Absolute (according to the docs.)
> Note that at this stage I can survive, as a relative solution is fine.
> But I'd like to know what the end verdict is, for the doco.
However, I *believe* that it will pull things out of the LD_LIBRARY_PATH
if you don't specify the entire path. So, using my above if I set the
LD_LIBRARY_PATH to /usr/lib, I can do:
System.load("libz.so.2.0");
And it will work. (If I don't set the LD_LIBRARY_PATH, by default it is
set to /usr/local/jdk1.1.5/lib/i386/green_threads).
But, if you give it the absolute path, it *should* work.
Any chance of having you simplifying your test program into less than
100 lines? *grin*
Nate
From owner-freebsd-java Mon Feb 2 22:09:01 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA29960
for java-outgoing; Mon, 2 Feb 1998 22:09:01 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from damon.com (OdcL3yx0kDO4AM0bfzk4CdWur6NUoMKD@damon.com [207.170.114.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29920
for <freebsd-java@FreeBSD.ORG>; Mon, 2 Feb 1998 22:08:54 -0800 (PST)
(envelope-from dap@damon.com)
Received: (from dap@localhost)
by damon.com (8.8.7/8.8.7) id AAA08954;
Tue, 3 Feb 1998 00:08:31 -0600 (CST)
(envelope-from dap)
From: Damon Permezel <dap@damon.com>
Message-Id: <199802030608.AAA08954@damon.com>
Subject: Re: jdk115 JNI requires ELF, gcc makes a.out
In-Reply-To: <34D6A37E.29B3C1AE@systemics.com> from Ian Grigg at "Feb 3, 98 04:56:30 am"
To: iang@systemics.com (Ian Grigg)
Date: Tue, 3 Feb 1998 00:08:31 -0600 (CST)
Cc: freebsd-java@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
"Ian Grigg sez: "
> Perhaps I'd better throw some questions in:
>
> * is "complete" synonymous with absolute?
No. Complete is synonymous with "add the suffix, and don't expect us to add
.dll or .so or .a"
> * is this a bug, or a misinterpretation?
The former.
> * should I be using System.loadLibrary?
Yes.
> * can I use absolute, relative, or what?
Add "/" to your LD_LIBRARY_PATH if you really want absolute to work.
> * ...
$$$
Some of this is opinion, and may be open to debate.
Like "if the specified path begins with a `/', why not attempt that first".
And "well, we don't want to encourage absolute paths, as this leads to
inflexibility".
From owner-freebsd-java Mon Feb 2 23:38:58 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA10669
for java-outgoing; Mon, 2 Feb 1998 23:38:58 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10658
for <freebsd-java@freebsd.org>; Mon, 2 Feb 1998 23:38:55 -0800 (PST)
(envelope-from hasty@rah.star-gate.com)
Received: from rah (localhost.star-gate.com [127.0.0.1])
by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id XAA27675
for <freebsd-java@freebsd.org>; Mon, 2 Feb 1998 23:38:49 -0800 (PST)
(envelope-from hasty@rah.star-gate.com)
Message-Id: <199802030738.XAA27675@rah.star-gate.com>
X-Mailer: exmh version 2.0gamma 1/27/96
To: freebsd-java@FreeBSD.ORG
Subject: WaitProblem now gone 8)
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Feb 1998 23:38:49 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
{hasty} java WaitProblem
Executing the command
Command should be running
Command should be done
{hasty}
This is with tonites build as of 8:30 PM (PST).
Cheers,
Amancio
From owner-freebsd-java Mon Feb 2 23:49:23 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA12079
for java-outgoing; Mon, 2 Feb 1998 23:49:23 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12066
for <freebsd-java@freebsd.org>; Mon, 2 Feb 1998 23:49:22 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id AAA21347;
Tue, 3 Feb 1998 00:49:21 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id AAA01022; Tue, 3 Feb 1998 00:49:20 -0700
Date: Tue, 3 Feb 1998 00:49:20 -0700
Message-Id: <199802030749.AAA01022@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Amancio Hasty <hasty@rah.star-gate.com>
Cc: freebsd-java@FreeBSD.ORG
Subject: Re: WaitProblem now gone 8)
In-Reply-To: <199802030738.XAA27675@rah.star-gate.com>
References: <199802030738.XAA27675@rah.star-gate.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
Amancio Hasty writes:
> {hasty} java WaitProblem
> Executing the command
> Command should be running
> Command should be done
> {hasty}
>
> This is with tonites build as of 8:30 PM (PST).
Yeah, yeah, yeah. I'm working on getting a new build out right now as
we speak, so hold onto your knickers. :)
Nate
From owner-freebsd-java Tue Feb 3 00:03:59 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA15256
for java-outgoing; Tue, 3 Feb 1998 00:03:59 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from livedev.livesystems.com (livedev.livesystems.com [207.211.32.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15240
for <freebsd-java@freebsd.org>; Tue, 3 Feb 1998 00:03:56 -0800 (PST)
(envelope-from tom.chappell@livesystems.com)
Received: from tom (tom.livesystems.com [207.211.32.70])
by livedev.livesystems.com (8.8.7/8.8.7) with SMTP id AAA08942;
Tue, 3 Feb 1998 00:03:27 -0800 (PST)
(envelope-from tom.chappell@livesystems.com)
Received: by localhost with Microsoft MAPI; Tue, 3 Feb 1998 00:02:47 -0800
Message-ID: <01BD3037.0F6BCEE0.tom.chappell@livesystems.com>
From: Tom Chappell <tom.chappell@livesystems.com>
To: "'Amancio Hasty'" <hasty@rah.star-gate.com>,
"freebsd-java@freebsd.org"
<freebsd-java@FreeBSD.ORG>
Subject: RE: WaitProblem now gone 8)
Date: Tue, 3 Feb 1998 00:02:47 -0800
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
Is this fix actually posted somewhere? The one pointed to by the www.freebsd.org/java page still has the waitFor ( ) problem.
-----Original Message-----
From: Amancio Hasty [SMTP:hasty@rah.star-gate.com]
Sent: Monday, February 02, 1998 11:39 PM
To: freebsd-java@freebsd.org
Subject: WaitProblem now gone 8)
{hasty} java WaitProblem
Executing the command
Command should be running
Command should be done
{hasty}
This is with tonites build as of 8:30 PM (PST).
Cheers,
Amancio
From owner-freebsd-java Tue Feb 3 00:12:21 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA16855
for java-outgoing; Tue, 3 Feb 1998 00:12:21 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16849
for <freebsd-java@freebsd.org>; Tue, 3 Feb 1998 00:12:20 -0800 (PST)
(envelope-from hasty@rah.star-gate.com)
Received: from rah (localhost.star-gate.com [127.0.0.1])
by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id AAA13230;
Tue, 3 Feb 1998 00:12:15 -0800 (PST)
(envelope-from hasty@rah.star-gate.com)
Message-Id: <199802030812.AAA13230@rah.star-gate.com>
X-Mailer: exmh version 2.0gamma 1/27/96
To: Tom Chappell <tom.chappell@livesystems.com>
cc: "freebsd-java@freebsd.org" <freebsd-java@FreeBSD.ORG>
Subject: Re: WaitProblem now gone 8)
In-reply-to: Your message of "Tue, 03 Feb 1998 00:02:47 PST."
<01BD3037.0F6BCEE0.tom.chappell@livesystems.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 03 Feb 1998 00:12:15 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
Sorry about that I posted to the wrong list -- that message was
meant to go to internal jdk developers. Don't mind me I had 3 hours
of sleep last nite then went today to the Dentist (noticed the
capitalization) to get my teeth cleaned --- Well let me tell you it is a
very very nice to way to keep you up 8)
Cheers,
Amancio
> Is this fix actually posted somewhere? The one pointed to by the www.freebsd.org/java page still has the waitFor ( ) problem.
>
> -----Original Message-----
> From: Amancio Hasty [SMTP:hasty@rah.star-gate.com]
> Sent: Monday, February 02, 1998 11:39 PM
> To: freebsd-java@freebsd.org
> Subject: WaitProblem now gone 8)
>
> {hasty} java WaitProblem
> Executing the command
> Command should be running
> Command should be done
> {hasty}
>
> This is with tonites build as of 8:30 PM (PST).
>
> Cheers,
> Amancio
>
>
From owner-freebsd-java Wed Feb 4 14:42:52 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA29329
for java-outgoing; Wed, 4 Feb 1998 14:42:52 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29313
for <freebsd-java@FreeBSD.ORG>; Wed, 4 Feb 1998 14:42:46 -0800 (PST)
(envelope-from hasty@rah.star-gate.com)
Received: (from hasty@localhost)
by rah.star-gate.com (8.8.8/8.8.8) id OAA03524
for freebsd-java@FreeBSD.ORG; Wed, 4 Feb 1998 14:42:41 -0800 (PST)
(envelope-from hasty)
Date: Wed, 4 Feb 1998 14:42:41 -0800 (PST)
From: Amancio Hasty <hasty@rah.star-gate.com>
Message-Id: <199802042242.OAA03524@rah.star-gate.com>
To: freebsd-java@FreeBSD.ORG
Subject: Highlight of a single Swing Jtable cell.
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
Howdy,
Currently, with Swing's JTable default behavior you can highlight a
row or a column . What I would like to do is to hightlight a single
cell, does anyone in the list knows how to do this?
Cheers,
Amancio
From owner-freebsd-java Fri Feb 6 00:00:12 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA21837
for java-outgoing; Fri, 6 Feb 1998 00:00:12 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21812;
Fri, 6 Feb 1998 00:00:07 -0800 (PST)
(envelope-from rb@gid.co.uk)
Received: from gid.co.uk (uucp@localhost)
by isbalham.ist.co.uk (8.8.7/8.8.4) with UUCP
id HAA00654; Fri, 6 Feb 1998 07:58:37 GMT
Received: from [194.32.164.2] by seagoon.gid.co.uk; Fri, 6 Feb 1998 07:52:14 GMT
X-Sender: rb@194.32.164.1
Message-Id: <l03020901b1006fd6f3c1@[194.32.164.2]>
In-Reply-To: <199802052141.NAA02458@hub.freebsd.org>
References: <199802051608.SAA23230@shadows.aeon.net> from mika ruohotie at
"Feb 5, 98 06:08:02 pm"
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 6 Feb 1998 07:48:50 +0000
To: announce@FreeBSD.ORG, database@FreeBSD.ORG, java@FreeBSD.ORG,
mobile@FreeBSD.ORG
From: Bob Bishop <rb@gid.co.uk>
Subject: Test
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
At 9:41 pm +0000 5/2/98, Jonathan M. Bresler wrote:
> please check your subscriptions.
--
Bob Bishop (0118) 977 4017 international code +44 118
rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK
From owner-freebsd-java Fri Feb 6 15:08:43 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA18764
for java-outgoing; Fri, 6 Feb 1998 15:08:43 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from proxy4.ba.best.com (root@proxy4.ba.best.com [206.184.139.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18757
for <freebsd-java@freebsd.org>; Fri, 6 Feb 1998 15:08:42 -0800 (PST)
(envelope-from GregoryC@stcinc.com)
Received: from starbase (carvalho.vip.best.com [205.149.168.27]) by proxy4.ba.best.com (8.8.8/8.8.BEST) with SMTP id PAA25427 for <freebsd-java@freebsd.org>; Fri, 6 Feb 1998 15:07:30 -0800 (PST)
Received: by localhost with Microsoft MAPI; Fri, 6 Feb 1998 15:05:14 -0800
Message-ID: <01BD3310.A0DC3000.GregoryC@stcinc.com>
From: Gregory Carvalho <GregoryC@stcinc.com>
To: "'freebsd-java@freebsd.org'" <freebsd-java@FreeBSD.ORG>
Subject: subscribe
Date: Fri, 6 Feb 1998 15:04:58 -0800
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
subscribe
From owner-freebsd-java Sat Feb 7 13:00:12 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA00631
for java-outgoing; Sat, 7 Feb 1998 13:00:12 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from kstreet.interlog.com (kws@kstreet.interlog.com [198.53.146.171])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00626
for <freebsd-java@freebsd.org>; Sat, 7 Feb 1998 13:00:08 -0800 (PST)
(envelope-from kws@kstreet.interlog.com)
Received: (from kws@localhost)
by kstreet.interlog.com (8.8.8/8.8.8) id PAA21069;
Sat, 7 Feb 1998 15:59:55 -0500 (EST)
(envelope-from kws)
Date: Sat, 7 Feb 1998 15:59:55 -0500 (EST)
Message-Id: <199802072059.PAA21069@kstreet.interlog.com>
From: Kevin Street <street@iName.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: freebsd-java@FreeBSD.ORG
Subject: Java bug with setMenuBar()
X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
I've found a bug (restriction? feature?) with setMenuBar. I'd like to
swap menu bars in my awt application in some circumstances. When I
call setMenuBar the entire application window moves up & left on the
screen. It works ok if I bracket the setMenuBar call with
setVisible(false) and show(), but the window flash looks ugly.
Any thoughts on why Java can't keep track of where it is when swapping
the menu bar?
Here's a stripped down program that exhibits the problem. It's only
about 130 lines so I'll just include it here - hopefully that's not
too excessive for those of you with expensive mail.
*** MenuBug.java ***
import java.awt.*;
import java.awt.event.*;
class MenuBug extends Frame
{
private MenuBar mbar1;
private MenuBar mbar2;
private int currentbar;
public static void main(String args[])
{
MenuBug window = new MenuBug("Menu Bug Demonstration Window");
window.show();
}
MenuBug(String title)
{
super(title);
addWindowListener(new AppWindowListener ());
setSize(500,300);
mbar1 = buildMenuBar(1);
mbar2 = buildMenuBar(2);
setMenuBar(mbar1);
currentbar = 1;
}
private void swapMenuBar()
{
// setVisible(false);
if (1 == currentbar) {
setMenuBar(mbar2);
currentbar = 2;
} else {
setMenuBar(mbar1);
currentbar = 1;
}
// show();
}
private void showLocation()
{
System.out.println("getInsets() returned " + getInsets());
System.out.println("getLocation() returned " + getLocation());
try
{
System.out.println("getLocationOnScreen() returned " +
getLocationOnScreen());
}
catch ( IllegalComponentStateException e )
{
System.out.println("Not on screen");
}
}
public void dispose()
{
setVisible(false);
super.dispose();
}
private class MIswapActionListener implements ActionListener
{
public void actionPerformed(ActionEvent e)
{
showLocation();
swapMenuBar();
showLocation();
}
}
private class MIwhereActionListener implements ActionListener
{
public void actionPerformed(ActionEvent e)
{
showLocation();
}
}
private class MIexitActionListener implements ActionListener
{
public void actionPerformed(ActionEvent e)
{
dispose();
}
}
private class AppWindowListener implements WindowListener
{
public void windowActivated(WindowEvent e) {}
public void windowClosed(WindowEvent e)
{
System.exit(0);
}
public void windowClosing(WindowEvent e)
{
dispose();
}
public void windowDeactivated(WindowEvent e) {}
public void windowDeiconified(WindowEvent e) {}
public void windowIconified(WindowEvent e) {}
public void windowOpened(WindowEvent e) {}
}
private MenuBar buildMenuBar(int which)
{
Menu fileMenu;
MenuBar mbar;
MenuItem mi;
mbar = new MenuBar();
fileMenu = new Menu("File");
fileMenu.add(mi = new MenuItem("Where"));
mi.addActionListener(new MIwhereActionListener());
fileMenu.add(mi = new MenuItem("Swap"));
mi.addActionListener(new MIswapActionListener());
if (1 == which) {
fileMenu.addSeparator();
fileMenu.add(mi = new MenuItem("Exit"));
mi.addActionListener(new MIexitActionListener());
}
mbar.add(fileMenu);
return mbar;
}
}
--
Kevin Street
street@iName.com
From owner-freebsd-java Sat Feb 7 13:17:05 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA02846
for java-outgoing; Sat, 7 Feb 1998 13:17:05 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02839
for <freebsd-java@FreeBSD.ORG>; Sat, 7 Feb 1998 13:17:00 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA00934;
Sat, 7 Feb 1998 14:16:55 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id OAA16691; Sat, 7 Feb 1998 14:16:53 -0700
Date: Sat, 7 Feb 1998 14:16:53 -0700
Message-Id: <199802072116.OAA16691@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Kevin Street <street@iName.com>
Cc: freebsd-java@FreeBSD.ORG
Subject: Re: Java bug with setMenuBar()
In-Reply-To: <199802072059.PAA21069@kstreet.interlog.com>
References: <199802072059.PAA21069@kstreet.interlog.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
> I've found a bug (restriction? feature?) with setMenuBar.
Have you tried your test program out with a 'reference' implementation
(aka, something distributed from SUN, such as their Solaris and/or Win32
port)? If not, it would be *real* helpful to the FreeBSD folks to know
whether or not this is a FreeBSD-specific bug or a generic JDK bug.
If the former, then we might be able to fix it, or it might be a
'feature' of the language/AWT implementation. If the latter, then we
most certainly *need* to fix it.
Thanks!
Nate
From owner-freebsd-java Sat Feb 7 14:15:37 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA14327
for java-outgoing; Sat, 7 Feb 1998 14:15:37 -0800 (PST)
(envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from kstreet.interlog.com (kws@kstreet.interlog.com [198.53.146.171])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14318
for <freebsd-java@FreeBSD.ORG>; Sat, 7 Feb 1998 14:15:32 -0800 (PST)
(envelope-from kws@kstreet.interlog.com)
Received: (from kws@localhost)
by kstreet.interlog.com (8.8.8/8.8.8) id RAA21251;
Sat, 7 Feb 1998 17:14:55 -0500 (EST)
(envelope-from kws)
Date: Sat, 7 Feb 1998 17:14:55 -0500 (EST)
Message-Id: <199802072214.RAA21251@kstreet.interlog.com>
From: Kevin Street <street@iName.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Nate Williams <nate@mt.sri.com>
Cc: freebsd-java@FreeBSD.ORG
Subject: Re: Java bug with setMenuBar()
In-Reply-To: <199802072116.OAA16691@mt.sri.com>
References: <199802072059.PAA21069@kstreet.interlog.com>
<199802072116.OAA16691@mt.sri.com>
X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"
Nate Williams writes:
>> I've found a bug (restriction? feature?) with setMenuBar.
>
>Have you tried your test program out with a 'reference' implementation
>(aka, something distributed from SUN, such as their Solaris and/or Win32
>port)? If not, it would be *real* helpful to the FreeBSD folks to know
>whether or not this is a FreeBSD-specific bug or a generic JDK bug.
Windows, eeww. Oh well, ok. I've just fired up a Windows 95 machine
that has the 1.1.4 jdk on it. I tried the FreeBSD generated
class files and also recompiled the .java on the Windows machine. Either
way works fine.
I had the same problem on 1.1.? on FreeBSD so it's not a new 1.1.5
bug. I'd previously assumed it was a lesstif weirdness untill the
1.1.5 FreeBSD binary on Motif showed up.
--
Kevin Street
street@iName.com