harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ivanov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-3731) [DRLVM] FinalizeStackTest failed in opt/srv mode on Win32
Date Tue, 24 Apr 2007 08:21:15 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491178
] 

Vladimir Ivanov commented on HARMONY-3731:
------------------------------------------

On my WinXP SP2 PentiumM CPU, 2Gb RAM this test failed with log:
------------- out ----------------------
PASS : java.lang.StackOverflowError

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
-----------------------------------------
------------- err -----------------------
Assertion failed: !is_unwindable(), file C:\harmony.top\drlvm\trunk\vm\vmcore\src\jni\jni_utils.cpp,
line 662

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
-----------------------------------------

I vote for this test exclusion on WinXP, x86 in opt+srv modes.

 thanks, Vladimir


> [DRLVM] FinalizeStackTest failed in opt/srv mode on Win32
> ---------------------------------------------------------
>
>                 Key: HARMONY-3731
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3731
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Win32, opt/srv mode
>            Reporter: Xiao-Feng Li
>
> This test case breaks from time to time, but hard to be reproduced. We suggest to keep
it in JIRA and exclude it for opt/srv modes test.
> Pavel Afremov has following comments, which are helpful for people fixing the bug:
>   1. In this case, fast asm helpers aren't used, because allocation of
>   finalizable objects always goes throw slow path.
>   2. It will be very nice to found what returns 3 error code. Correct me
>   if I wrong, this code is returned when top level thread exception handler
>   catch unprocessed java exception. It's a different situation. When VM
>   crashed with unprocessed SOE in fast path asm helpers it returns 128 error
>   code.
>   3. It looks very strange that test works in client mode and doesn't
>   work in server. For VM side (exception handling and helpers) there is no
>   difference between these two modes.

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


Mime
View raw message