From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Neil Jerram" Newsgroups: gmane.lisp.guile.bugs Subject: Re: [PATCH] Final: thread lock nesting debugging Date: Thu, 20 Nov 2008 00:22:22 +0000 Message-ID: <49dd78620811191622w3e8f22eg28c57e051a86dc8b@mail.gmail.com> References: <3ae3aa420811162042n4b5d50e3i136a9f7b00262a69@mail.gmail.com> <49dd78620811191514m6e73438esd4f1474c9926880d@mail.gmail.com> <49dd78620811191521vdc920cenacc5c4d4040a37a1@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1227140559 14149 80.91.229.12 (20 Nov 2008 00:22:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 20 Nov 2008 00:22:39 +0000 (UTC) Cc: bug-guile@gnu.org To: linasvepstas@gmail.com Original-X-From: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Thu Nov 20 01:23:41 2008 Return-path: Envelope-to: guile-bugs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1L2xKf-0006zN-8p for guile-bugs@m.gmane.org; Thu, 20 Nov 2008 01:23:41 +0100 Original-Received: from localhost ([127.0.0.1]:56002 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L2xJV-0008Ik-UG for guile-bugs@m.gmane.org; Wed, 19 Nov 2008 19:22:29 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L2xJR-0008H3-VB for bug-guile@gnu.org; Wed, 19 Nov 2008 19:22:26 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L2xJQ-0008Ge-CN for bug-guile@gnu.org; Wed, 19 Nov 2008 19:22:25 -0500 Original-Received: from [199.232.76.173] (port=43871 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L2xJQ-0008Gb-6o for bug-guile@gnu.org; Wed, 19 Nov 2008 19:22:24 -0500 Original-Received: from rv-out-0708.google.com ([209.85.198.246]:59856) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L2xJP-0006aC-Tv for bug-guile@gnu.org; Wed, 19 Nov 2008 19:22:24 -0500 Original-Received: by rv-out-0708.google.com with SMTP id k29so199916rvb.6 for ; Wed, 19 Nov 2008 16:22:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=eNi2GYLTpOHLn/ZFKSzwTLW3ZTU355CwBOrzm1lmTnY=; b=gF8L6ZhM3OzvVgki1cldQfx3qd44JQhx3dEpiPO4iyzLZ82CCGSq8BjflYsJErrxQ0 tmP7mf9hc9oMxFRoa4FnugG/jCmUQY6RoT3BNzYSnJXrzOMak00w95wCgTl9GkSh00WB dNWqajkstChIJOoWFbJ3INmjpwnOXqvT1Zx5k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=wKP8T/vkoA1rMo2X9jlADFCNDQ3NdPSTnRoY4tcMFnn40GTpHhPzMbe8h6DzFt01W0 RwYxizUmQl8NSZypNs9f4kuA4Z9m+GTGxlwdqP1tAdtGd0PfLrFTmA+GV7BPH+IJISdJ /GLc/x6bJ8r1kHzsC9MSu82JypEadZkmldoKU= Original-Received: by 10.140.192.9 with SMTP id p9mr887816rvf.236.1227140542982; Wed, 19 Nov 2008 16:22:22 -0800 (PST) Original-Received: by 10.140.142.15 with HTTP; Wed, 19 Nov 2008 16:22:22 -0800 (PST) In-Reply-To: <49dd78620811191521vdc920cenacc5c4d4040a37a1@mail.gmail.com> Content-Disposition: inline X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: bug-guile@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GUILE, GNU's Ubiquitous Extension Language" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Errors-To: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.bugs:4119 Archived-At: 2008/11/19 Neil Jerram : > > Also I wondered if there are already tools to debug this kind of thing > (without new Guile code), and a quick search finds this [1], which > suggests that helgrind could catch bad lock ordering for us. > > [1] http://www.network-theory.co.uk/docs/valgrind/valgrind_113.html Well, in fact "valgrind --tool=helgrind guile" does produce tons of output describing apparent lock ordering problems. I imagine some will be false positives, but there's a lot to work through. Neil