You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Eugene S. Ostrovsky (JIRA)" <ji...@apache.org> on 2007/04/20 12:22:15 UTC
[jira] Created: (HARMONY-3713) [classlib][launcher]
DetachCurrentThread() is called before DestroyJavaVM()
[classlib][launcher] DetachCurrentThread() is called before DestroyJavaVM()
---------------------------------------------------------------------------
Key: HARMONY-3713
URL: https://issues.apache.org/jira/browse/HARMONY-3713
Project: Harmony
Issue Type: Bug
Components: Classlib
Reporter: Eugene S. Ostrovsky
Spec ( http://java.sun.com/j2se/1.5.0/docs/guide/jni/spec/invocation.html#wp16553 ) says:
"The main thread cannot detach itself from the VM. Instead, it must call DestroyJavaVM() to unload the entire VM"
In current launcher implementation (main.c) we have:
...
(*jvm)->DetachCurrentThread(jvm);
(*jvm)->DestroyJavaVM (jvm);
...
This bug affects jvmti: HARMONY-3532
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HARMONY-3713) [classlib][launcher]
DetachCurrentThread() is called before DestroyJavaVM()
Posted by "Tim Ellison (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Ellison resolved HARMONY-3713.
----------------------------------
Resolution: Fixed
Thanks Eugene.
Patch applied to LUNI module and jdktools at repo revision 530924.
Please check that it was applied as you expected.
> [classlib][launcher] DetachCurrentThread() is called before DestroyJavaVM()
> ---------------------------------------------------------------------------
>
> Key: HARMONY-3713
> URL: https://issues.apache.org/jira/browse/HARMONY-3713
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Reporter: Eugene S. Ostrovsky
> Assigned To: Tim Ellison
> Attachments: H3713-Fix.patch
>
>
> Spec ( http://java.sun.com/j2se/1.5.0/docs/guide/jni/spec/invocation.html#wp16553 ) says:
> "The main thread cannot detach itself from the VM. Instead, it must call DestroyJavaVM() to unload the entire VM"
> In current launcher implementation (main.c) we have:
> ...
> (*jvm)->DetachCurrentThread(jvm);
> (*jvm)->DestroyJavaVM (jvm);
> ...
> This bug affects jvmti: HARMONY-3532
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-3713) [classlib][launcher]
DetachCurrentThread() is called before DestroyJavaVM()
Posted by "Eugene S. Ostrovsky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eugene S. Ostrovsky updated HARMONY-3713:
-----------------------------------------
Patch Info: [Patch Available]
> [classlib][launcher] DetachCurrentThread() is called before DestroyJavaVM()
> ---------------------------------------------------------------------------
>
> Key: HARMONY-3713
> URL: https://issues.apache.org/jira/browse/HARMONY-3713
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Reporter: Eugene S. Ostrovsky
> Attachments: H3713-Fix.patch
>
>
> Spec ( http://java.sun.com/j2se/1.5.0/docs/guide/jni/spec/invocation.html#wp16553 ) says:
> "The main thread cannot detach itself from the VM. Instead, it must call DestroyJavaVM() to unload the entire VM"
> In current launcher implementation (main.c) we have:
> ...
> (*jvm)->DetachCurrentThread(jvm);
> (*jvm)->DestroyJavaVM (jvm);
> ...
> This bug affects jvmti: HARMONY-3532
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (HARMONY-3713) [classlib][launcher]
DetachCurrentThread() is called before DestroyJavaVM()
Posted by "Tim Ellison (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Ellison closed HARMONY-3713.
--------------------------------
No response, assuming ok.
> [classlib][launcher] DetachCurrentThread() is called before DestroyJavaVM()
> ---------------------------------------------------------------------------
>
> Key: HARMONY-3713
> URL: https://issues.apache.org/jira/browse/HARMONY-3713
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Reporter: Eugene S. Ostrovsky
> Assignee: Tim Ellison
> Attachments: H3713-Fix.patch
>
>
> Spec ( http://java.sun.com/j2se/1.5.0/docs/guide/jni/spec/invocation.html#wp16553 ) says:
> "The main thread cannot detach itself from the VM. Instead, it must call DestroyJavaVM() to unload the entire VM"
> In current launcher implementation (main.c) we have:
> ...
> (*jvm)->DetachCurrentThread(jvm);
> (*jvm)->DestroyJavaVM (jvm);
> ...
> This bug affects jvmti: HARMONY-3532
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HARMONY-3713) [classlib][launcher]
DetachCurrentThread() is called before DestroyJavaVM()
Posted by "Tim Ellison (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Ellison reassigned HARMONY-3713:
------------------------------------
Assignee: Tim Ellison
> [classlib][launcher] DetachCurrentThread() is called before DestroyJavaVM()
> ---------------------------------------------------------------------------
>
> Key: HARMONY-3713
> URL: https://issues.apache.org/jira/browse/HARMONY-3713
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Reporter: Eugene S. Ostrovsky
> Assigned To: Tim Ellison
> Attachments: H3713-Fix.patch
>
>
> Spec ( http://java.sun.com/j2se/1.5.0/docs/guide/jni/spec/invocation.html#wp16553 ) says:
> "The main thread cannot detach itself from the VM. Instead, it must call DestroyJavaVM() to unload the entire VM"
> In current launcher implementation (main.c) we have:
> ...
> (*jvm)->DetachCurrentThread(jvm);
> (*jvm)->DestroyJavaVM (jvm);
> ...
> This bug affects jvmti: HARMONY-3532
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-3713) [classlib][launcher]
DetachCurrentThread() is called before DestroyJavaVM()
Posted by "Eugene S. Ostrovsky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eugene S. Ostrovsky updated HARMONY-3713:
-----------------------------------------
Attachment: H3713-Fix.patch
Attached patch:
H3713-Fix.patch
Proposed fix
> [classlib][launcher] DetachCurrentThread() is called before DestroyJavaVM()
> ---------------------------------------------------------------------------
>
> Key: HARMONY-3713
> URL: https://issues.apache.org/jira/browse/HARMONY-3713
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Reporter: Eugene S. Ostrovsky
> Attachments: H3713-Fix.patch
>
>
> Spec ( http://java.sun.com/j2se/1.5.0/docs/guide/jni/spec/invocation.html#wp16553 ) says:
> "The main thread cannot detach itself from the VM. Instead, it must call DestroyJavaVM() to unload the entire VM"
> In current launcher implementation (main.c) we have:
> ...
> (*jvm)->DetachCurrentThread(jvm);
> (*jvm)->DestroyJavaVM (jvm);
> ...
> This bug affects jvmti: HARMONY-3532
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.