You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Serguei Zapreyev (JIRA)" <ji...@apache.org> on 2006/09/26 03:08:51 UTC
[jira] Commented: (HARMONY-1573) [drlvm][kernel] Some minor issues
in j.l.Runtime implementation
[ http://issues.apache.org/jira/browse/HARMONY-1573?page=comments#action_12437708 ]
Serguei Zapreyev commented on HARMONY-1573:
-------------------------------------------
Sorry for some inconvenience. The attachement #5 is the test #1 mentioned in the
description. The attachement #4 is the test #2. The attachements #3 and #1 form the test #3.
The attachement #2 is the test #4.
> [drlvm][kernel] Some minor issues in j.l.Runtime implementation
> ---------------------------------------------------------------
>
> Key: HARMONY-1573
> URL: http://issues.apache.org/jira/browse/HARMONY-1573
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Serguei Zapreyev
> Priority: Minor
> Attachments: klazz.java, Test2.java, Test2.java, Test2.java, Test2.java
>
>
> Some defects in Runtime impl:
> - Impl can keep hanging process on Windows after VM finish (test #1).
> Restoring the noninheritable i/o handles resolves the issue.
> - "IOE: Stream closed" isn't risen on available() request on Linux if a stream is closed (test #2).
> Taking into consideration some additional error conditions for poll() resolves the issue.
> - Throwing an incorrect exit value after destroy() invocation on Windows (test #3).
> Changing the exit code for a terminated process resolves the issue.
> - Stream's available() method should return number of all accessible bytes on Linux as well (test #4).
> Using the ioctl request resolves the issue if possible
> - Runtime.addShutdownHook(Thread) doesn't throw IAE (test #5, the test should be added by its author).
> Checking the state of a being added thread resolves the issue
> - VM hangs on attempt to add/remove shutdown hooks while shutdown sequence (test #6, the test should be added by its author).
> Eliminating a needless synchronization resolves the issue.
> I'm going to attach the corresponding tests.
--
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