You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Geir Magnusson Jr (JIRA)" <ji...@apache.org> on 2006/08/02 23:06:16 UTC

[jira] Resolved: (HARMONY-926) classlib's launcher needs more functional and independent hythread from drlvm

     [ http://issues.apache.org/jira/browse/HARMONY-926?page=all ]

Geir Magnusson Jr resolved HARMONY-926.
---------------------------------------

    Resolution: Fixed

Applied and tested on Ubuntu 6

Committed in r428149


> classlib's launcher needs more functional and independent hythread from drlvm
> -----------------------------------------------------------------------------
>
>                 Key: HARMONY-926
>                 URL: http://issues.apache.org/jira/browse/HARMONY-926
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Andrey Chernyshev
>         Assigned To: Geir Magnusson Jr
>         Attachments: hythreads-patch.patch
>
>
> This issue is an addition to HARMONY-857.
> I finally figured out what was the cause of missing symbols in libhythr.so, there were two issues around that:
> - hythr was linked with vmcore  (hence the launcher didn't work until vmcore.so is loaded)  while it should be linked directly with the apr;
> - hythread library was missing hythread_monitor_notify  and hythread_exit functions - they weren't needed by the classlib itself, but they are needed for the launcher.
> Here will be a patch to the DRLVM's hythreads which addresses the above two issues.
> (I've also untabified & sorted hythr.def and hythr.exp).
> With this patch applied, I was able to run Eclipse with drlvm under the classlib's launcher both on Windows and Linux.
> Note: I had to replace libhyzlib.so with zlib.so on Linux to avoid segfaults (on some machines workaround mentioned at HARMONY-853 can be helpful). I didn't include the replacement into this patch.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira