You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexey Varlamov (JIRA)" <ji...@apache.org> on 2007/05/31 14:56:15 UTC
[jira] Updated: (HARMONY-4006) [drlvm][init] Eclipse launcher can't
start Harmony VM using JNI Invocation API.
[ https://issues.apache.org/jira/browse/HARMONY-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov updated HARMONY-4006:
-------------------------------------
Component/s: DRLVM
Summary: [drlvm][init] Eclipse launcher can't start Harmony VM using JNI Invocation API. (was: Eclipse launcher can't start Harmony VM using JNI Invocation API.)
> [drlvm][init] Eclipse launcher can't start Harmony VM using JNI Invocation API.
> -------------------------------------------------------------------------------
>
> Key: HARMONY-4006
> URL: https://issues.apache.org/jira/browse/HARMONY-4006
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: Windows
> Reporter: Andrew Niefer
> Attachments: eclipse_1018.dll
>
>
> See also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=189690
> We would like for the eclipse launcher to be able to start the harmony vm using the JNI invocation API.
> The eclipse launcher does not know anything about the port library. It looks for the symbol "JNI_CreateJavaVM" and calls it. If we modify the eclipse launcher to find "_JNI_CreateJavaVM@12" from the harmonyvm.dll, then the result is the following crash:
> Thread [1] (Suspended: Signal 'SIGSEGV' received. Description: Segmentation fault.)
> 2 harmonyvm!?classloader_find_native@@YAP6AXXZQAUMethod@@@Z() 0x00a8ecd8
> 1 <symbol is not available> 0x00000000
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.