You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Nikolay Kuznetsov (JIRA)" <ji...@apache.org> on 2006/10/02 13:50:25 UTC

[jira] Updated: (HARMONY-1537) Thread.currentThread().isAlive() returns false

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

Nikolay Kuznetsov updated HARMONY-1537:
---------------------------------------

    Attachment: HARMONY-1537_updated.patch

Sorry, I've confused thread name with Thread.toString, updated patch corrects name to be compatible with Sun's jdk.
And back to the question whether this patch needed at all, three was an issue to make tests pass as much as possible, while HARMONY-1582 is a long discussion, this one will help, I hope.  

> Thread.currentThread().isAlive() returns false
> ----------------------------------------------
>
>                 Key: HARMONY-1537
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1537
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Elena Semukhina
>         Attachments: HARMONY-1537.patch, HARMONY-1537_updated.patch
>
>
> Kernel unit test ThreadTest.testIsAliveCurrent() fails now because of Thread.currentThread().isAlive() returns false. 
> The following test case reproduces the issue:
> public class Test {
>     public static void main(String[] args) {
>         System.out.println("true = " + Thread.currentThread().isAlive());
>     }
> }
> Only DRLVM prints "true = false" :(

-- 
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