You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Pavel Rebriy (JIRA)" <ji...@apache.org> on 2007/04/06 12:30:32 UTC
[jira] Created: (HARMONY-3585) [drlvm][windows]
shutdown.TestFatalError fails on interpreter
[drlvm][windows] 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
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.
[jira] Updated: (HARMONY-3585) [drlvm][windows]
shutdown.TestFatalError fails on interpreter
Posted by "Pavel Rebriy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Rebriy updated HARMONY-3585:
----------------------------------
Attachment: shutdown_TestFatalError_exclude.patch
Here is the patch for test exclude.
> [drlvm][windows] 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
> 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.
[jira] Resolved: (HARMONY-3585) [drlvm][jni]
shutdown.TestFatalError fails on interpreter
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky resolved HARMONY-3585.
----------------------------------------
Resolution: Fixed
The patch changes interface with interpreter to pass file descriptor instead of FILE* to stack_dump
functions. This workarounds the problem on windows that recognizes stdout in different DLLs
differently.
Patch applied at 541322. The shutdown.TestFatalError test works on all platforms both on JIT and 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.
[jira] Assigned: (HARMONY-3585) [drlvm][windows]
shutdown.TestFatalError fails on interpreter
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky reassigned HARMONY-3585:
------------------------------------------
Assignee: Gregory Shimansky
> [drlvm][windows] 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.
[jira] Closed: (HARMONY-3585) [drlvm][jni] shutdown.TestFatalError
fails on interpreter
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky closed HARMONY-3585.
--------------------------------------
No response, assuming ok.
> [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
> Assignee: 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.
[jira] Updated: (HARMONY-3585) [drlvm][jni] shutdown.TestFatalError
fails on interpreter
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ 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.