|
From: | Morten Hustveit |
Subject: | [bug #35263] libobjc2 can enter a deadlock during dtable initialization |
Date: | Sat, 07 Jan 2012 17:00:20 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 |
URL: <http://savannah.gnu.org/bugs/?35263> Summary: libobjc2 can enter a deadlock during dtable initialization Project: GNUstep Submitted by: mortenhustveit Submitted on: Sat 07 Jan 2012 05:00:19 PM GMT Category: Libraries Severity: 3 - Normal Item Group: Bug Status: None Privacy: Public Assigned to: None Open/Closed: Open Discussion Lock: Any _______________________________________________________ Details: `dtable_for_class' contains some logic for waiting for an `initialize' call in another thread. This seems to break when the other thread is similarly waiting for us. I have attached a test-case which reproduces this behavior on every run on my computer using revision 28758 on GNU/Linux. I have also attached the Helgrind log of a single run. _______________________________________________________ File Attachments: ------------------------------------------------------- Date: Sat 07 Jan 2012 05:00:19 PM GMT Name: libobjc2-deadlock.m Size: 781B By: mortenhustveit <http://savannah.gnu.org/bugs/download.php?file_id=24758> ------------------------------------------------------- Date: Sat 07 Jan 2012 05:00:19 PM GMT Name: helgrind.txt Size: 17kB By: mortenhustveit <http://savannah.gnu.org/bugs/download.php?file_id=24759> _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?35263> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |