RFR [XS] JDK-6616502: JNI specification should discuss multiple invocations of DetachCurrentThread
Daniel D. Daugherty
daniel.daugherty at oracle.com
Fri Apr 25 19:54:13 UTC 2014
Thumbs up.
Dan
On 4/25/14 9:14 AM, David Simms wrote:
> JDK-6616502 <https://bugs.openjdk.java.net/browse/JDK-6616502>:
>
> JNI Specificatio
> <http://docs.oracle.com/javase/8/docs/technotes/guides/jni/spec/jniTOC.html>n
> should discuss multiple invocations of DetachCurrentThread Slight
> improvement to DetachCurrentThread()
> <http://docs.oracle.com/javase/8/docs/technotes/guides/jni/spec/invocation.html#DetachCurrentThread>:
> Similar to wording for "attach"; "Trying to detach a thread that is
> already detached is a no-op".
>
> Web review here: http://cr.openjdk.java.net/~dsimms/jnispec/6616502/
> <http://cr.openjdk.java.net/%7Edsimms/jnispec/6616502/>
>
> *Old Text*
> *New Text*
>
>
> DetachCurrentThread
>
> |jint DetachCurrentThread(JavaVM *vm);|
>
> Detaches the current thread from a Java VM. All Java monitors held by
> this thread are released. All Java threads waiting for this thread to
> die are notified.
>
> The main thread can be detached from the VM.
>
>
> DetachCurrentThread
>
> |jint DetachCurrentThread(JavaVM *vm);|
>
> Detaches the current thread from a Java VM. All Java monitors held by
> this thread are released. All Java threads waiting for this thread to
> die are notified.
>
> The main thread can be detached from the VM.
>
> Trying to detach a thread that is not attached is a no-op.
>
>
More information about the hotspot-dev
mailing list