From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <java-prs-return-8004-listarch-java-prs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 11563 invoked by alias); 14 Apr 2006 18:57:49 -0000
Received: (qmail 11542 invoked by uid 48); 14 Apr 2006 18:57:49 -0000
Date: Fri, 14 Apr 2006 18:57:00 -0000
Subject: [Bug libgcj/27170]  New: Deadlock in garbage collector
X-Bugzilla-Reason: CC
Message-ID: <bug-27170-83@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: java-prs@gcc.gnu.org
From: "green at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:java-prs-subscribe@gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/java-prs/>
List-Post: <mailto:java-prs@gcc.gnu.org>
List-Help: <mailto:java-prs-help@gcc.gnu.org>, <http://gcc.gnu.org/ml/#faqs>
Sender: java-prs-owner@gcc.gnu.org
X-SW-Source: 2006-q2/txt/msg00104.txt.bz2
List-Id: <java-prs.sourceware.org>

I believe I've identified a deadlock that is periodically reproducible
with Eclipse running on FC5.  I'll attach the stack trace to this bug
report.  See threads 4 and 13.

1. Thread 4 aquires the GC lock and starts a GC
2. Thread 13 dlopens a .so, acquiring a glibc maintained lock
3. Thread 13 tries to acquire the GC lock while registering classes
4. Thread 4 tries to acquire the glibc lock in dl_iterate_phdr

...and we're deadlocked.


-- 
           Summary: Deadlock in garbage collector
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgcj
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: green at redhat dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27170