unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Subject: Re: [PATCH] Final: thread lock nesting debugging
Date: Tue, 18 Nov 2008 14:26:09 +0100	[thread overview]
Message-ID: <87od0d413i.fsf@gnu.org> (raw)
In-Reply-To: 3ae3aa420811162042n4b5d50e3i136a9f7b00262a69@mail.gmail.com

Hello,

"Linas Vepstas" <linasvepstas@gmail.com> writes:

> I've been seeing all sorts of deadlocks in guile, and so I wrote a small
> debugging utility to try to track down the problems.  I'd like to see
> this patch included in future versions of guile.

FWIW, I'm reluctant to committing this patch for various reasons:
intrusion, non-genericity, bitrot of conditional code as Han-Wen noted,
non-C89ness, pollution outside of the `scm_' namespace, incorrect style.

Another reason is that pthread libraries are sometimes able to debug
deadlocks by themselves.  NetBSD's performs several run-time checks by
default [0].  Another solution is the explicit use of error-checking
mutexes, as with the patch at [1].  What do you think?

Thanks,
Ludo'.

[0] http://thread.gmane.org/gmane.lisp.guile.devel/6656
[1] http://thread.gmane.org/gmane.lisp.guile.devel/6733





  parent reply	other threads:[~2008-11-18 13:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-17  4:42 [PATCH] Final: thread lock nesting debugging Linas Vepstas
2008-11-17 13:21 ` Han-Wen Nienhuys
2008-11-18 13:26 ` Ludovic Courtès [this message]
2008-11-19 23:14 ` Neil Jerram
2008-11-19 23:21   ` Neil Jerram
2008-11-20  0:22     ` Neil Jerram
2008-11-20 16:03   ` Linas Vepstas
2008-11-20 18:33     ` Linas Vepstas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87od0d413i.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guile@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).