Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <33337022.1176464475877.JavaMail.jira@brutus>
Date: Fri, 13 Apr 2007 04:41:15 -0700 (PDT)
From: "George Timoshenko (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Updated: (HARMONY-3649) [drlvm] SPECjbb2005 intermittently
 fails on EM64T in server mode
In-Reply-To: <5759296.1176464475648.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HARMONY-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Timoshenko updated HARMONY-3649:
---------------------------------------

    Attachment: stack

example of call stack


> [drlvm] SPECjbb2005 intermittently fails on EM64T in server mode
> ----------------------------------------------------------------
>
>                 Key: HARMONY-3649
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3649
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: EM64T
>            Reporter: George Timoshenko
>         Attachments: stack
>
>
> The failure is very unstable.
> You can get only 1 failure from 10 runs.
> Or see 3 failures in a row.
> The failure allways looks like a segfault when some new object is being allocated in STL code. (iterator, new item in a container, just a new std::string...)
> Usually the STL code is being called from execution manager or Jitrino.OPT code. But the caller's code is OK and does not give any clue.
> the first time the failure was observed is April 4.

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