harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Pervov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-4006) [drlvm][init] Eclipse launcher can't start Harmony VM using JNI Invocation API.
Date Fri, 29 Jun 2007 09:02:05 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509066
] 

Pavel Pervov commented on HARMONY-4006:
---------------------------------------

With eclipse-way-valid :) path specified and patches from HARMONY-4038 and from this JIRA
applied eclipse starts, but do not find Harmony JRE.

But I think this is different issue which is not related to starting with standard launcher
in any way.

Mission accomplished. :) I believe these patches will be applied as soon as code unfrozen.

> [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, JNI_invocation_no_decorate.patch, library.zip
>
>
> 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.


Mime
View raw message