Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <30133157.1176741135532.JavaMail.jira@brutus>
Date: Mon, 16 Apr 2007 09:32:15 -0700 (PDT)
From: "Ilya Berezhniuk (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_12489166 ] 

Ilya Berezhniuk commented on HARMONY-3666:
------------------------------------------

I recently investigated this problem and found no solution in current design.

I observed such deadlock when free() was called second time on same pointer.
glipc acquires lock in free() and crashes, then crash handler invokes fork() and hangs, likely trying to allocate memory or free memory. I tried to invoke crash handler after returning from signal handler, and tried to process crash in separate thread - it did not fixed deadlock.

Looks like fork() usage for getting debug information through addr2line is a wrong way, but alternative ways are too expensive.


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