Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <19235757.1177374015445.JavaMail.jira@brutus>
Date: Mon, 23 Apr 2007 17:20:15 -0700 (PDT)
From: "Xiao-Feng Li (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Created: (HARMONY-3731) [DRLVM] FinalizeStackTest failed in
 opt/srv mode on Win32
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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