Hi,
I've got a bit of follow-up on Jason's Thread.stop() message. I've found a
bug in Kaffe's Thread.stop(Thowable object) method. The following code, legal
under Java 1.1, 1.2 and 1.3 exposes it:
---ThreadStop.java---
class Runner extends Thread {
public void run() {
try
(2) What sort of "process model" are you after? Have you considered
CSP?
Just a quick comment about that one:
When we say "process model" we mean "process" as in Unix process, i.e.,
an abstraction for a separate entity that include one or more threads of
execution. The emphasis is on
Jason Baker writes:
I noticed some inconsistency in Thread.stop(Throwable). When an
interruptable thread is stopped, the we get the calling thread's
stacktrace. When a thread is asynchronously killed, we get the dying
thread's stacktrace, but not in the exception stop was passed in. I
Archie Cobbs [EMAIL PROTECTED] writes:
Email me a simple test case and I'll run it under both kaffe and JDK 1.2.
Weird. Blackdown 1.2.2 doesn't seem to asynchronously stop threads at
all, while jdk 1.1.7 can do it some of the time. Neither one seems to
throw an exception with a stack trace
I was under the impression that methods like Thread.stop() were
removed from the JDK or replaced with no-ops. I seem to remember
that they were never implemented in Netscape's JVM. The whole
concept of stoping a thread seems like a bad idea, a thread
should expire due to natural causes.
Here
I also found this note in kaffe/FAQ/FAQ.pthreads
* We do not support asynchronous exceptions via Thread.stop()
Mo Dejong
Red Hat Inc.
On Mon, 22 May 2000, Mo DeJong wrote:
I was under the impression that methods like Thread.stop() were
removed from the JDK or replaced with no-ops. I seem
Jason Baker wrote:
Thread.stop is dangerous, but without a process model there is really
no alternative. I'm using it to halt infinite loops, which is why I
need the stack trace.
I'm pretty sure that the official position from Sun is that there is
no way to stop uncooperative threads
to explain when stop works
in 1.1.7.
Does anyone think that Thread.waitOn should emulate jdk behavior and
clear out the stack trace from a Thread.stop() exception before
throwing it?
Jason
--
1.2.2:
nephi(53) java Die
On Mon, 22 May 2000, Jason Baker wrote:
Mo DeJong [EMAIL PROTECTED] writes:
I was under the impression that methods like Thread.stop() were
removed from the JDK or replaced with no-ops. I seem to remember
that they were never implemented in Netscape's JVM. The whole
concept of stoping
