From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: bug-guile@gnu.org
Subject: Re: [PATCH] Final: thread lock nesting debugging
Date: Mon, 17 Nov 2008 11:21:08 -0200 [thread overview]
Message-ID: <gfrr46$osq$1@ger.gmane.org> (raw)
In-Reply-To: <3ae3aa420811162042n4b5d50e3i136a9f7b00262a69@mail.gmail.com>
Linas Vepstas escreveu:
> 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.
>
> I found one bug with this tool, and have submitted a patch for that
> already. It looks like there's another bug involving signals --
> there is a probably deadlock in garbage collection if a signal
> is sent at just the wrong time. The bug can be seen by enabling
> this patch, and then running 'make check'. I'm going to ignore
> this, as I'm not worried about signals right now.
>
> This is my "final" version of this patch, I'd sent a beta version
> a few days ago. Its "final" because I'm not anticipating any
> further changes.
Would it be possible to have this be a runtime switch? My experience
is that conditional code in GUILE (especially the debugging ones) tend
to bitrot very quickly. Also, they don´t help anyone who is not compiling
their own GUILE.
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2008-11-17 13:21 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 [this message]
2008-11-18 13:26 ` Ludovic Courtès
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='gfrr46$osq$1@ger.gmane.org' \
--to=hanwen@xs4all.nl \
--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).