harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Shimansky (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-3585) [drlvm][jni] shutdown.TestFatalError fails on interpreter
Date Wed, 16 May 2007 14:52:16 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Gregory Shimansky updated HARMONY-3585:

    Summary: [drlvm][jni] shutdown.TestFatalError fails on interpreter  (was: [drlvm][windows]
shutdown.TestFatalError fails on interpreter)

> [drlvm][jni] shutdown.TestFatalError fails on interpreter
> ---------------------------------------------------------
>                 Key: HARMONY-3585
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3585
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Windows
>            Reporter: Pavel Rebriy
>         Assigned To: Gregory Shimansky
>         Attachments: shutdown_TestFatalError_exclude.patch
> Test shutdown.TestFatalError fails on interpreter after Gregory Shimansky commit revisions
525916 & 525918.
> Gregory changed interface between interpreter and vmcore component. Interpreter accepts
file stream from vmcore now. Interpreter fails when it uses "stdout" stream  from vmcore.
> The problem is in windows runtime. Interpreter library and vmcore library are linked
with their own static runtimes. That is "stdout" stream for vmcore differs from interpreter
one. Lock mechanism for "stdout" stream is different than file stream, so runtime perceives
what stream is passed as the parameter and calls file lock or "stdout" lock. If "stdout" stream
structure came from different library this check fails and runtime tries to call file lock
not "stdout" stream lock.
> The solution is correct build system to use dynamic runtime for all libraries in DRLVM
and classlib.
> The test shutdown.TestFatalError should be excluded from Windows system.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message