Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <21523360.1176820215742.JavaMail.jira@brutus>
Date: Tue, 17 Apr 2007 07:30:15 -0700 (PDT)
From: "Gregory Shimansky (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Commented: (HARMONY-3666) [drlvm] crash handler sometimes
 deadlocks
In-Reply-To: <17739019.1176732795575.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-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489408 ] 

Gregory Shimansky commented on HARMONY-3666:
--------------------------------------------

I am not sure how to check for the locked condition of C heap lock. This mutex is internal to glibc and there is no external access to it.

> [drlvm] crash handler sometimes deadlocks 
> ------------------------------------------
>
>                 Key: HARMONY-3666
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3666
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Linux@ia32
>            Reporter: Alexey Varlamov
>         Attachments: gdb_all_bt.2.txt, gdb_all_bt.txt
>
>
> Running AWT tests with release VM, ~ each 3rd run hangs during stack dump. Usually this happens if SIGSEGV happens early enough (up to 6-8 tests run), probably interfered with compilation. I did not seen hangs on debug build, probably because of different timings.
> Anyway, almost always VM just prints "SIGSEGV in VM code." and either hangs or aborts. 

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