unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: "Julian Graham" <joolean@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: deadlock in scm_join_thread(_timed)
Date: Wed, 20 May 2009 19:24:57 +0100	[thread overview]
Message-ID: <87my97zl6u.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <2bc5f8210805261953s18bef0b9i9e32ee7cb4486c0e@mail.gmail.com> (Julian Graham's message of "Mon\, 26 May 2008 22\:53\:20 -0400")

"Julian Graham" <joolean@gmail.com> writes:

> Hi Neil,
>
>> Based on the synopsis above, I agree that moving step 1 inside the loop
>> should fix this.  In addition, though, I think it would be very good if we
>> could add a minimal test that currently reproduces the deadlock, and so will
>> serve to guard against future regressions here.  Do you have such a test?
>
> I don't -- it seems to be pretty dependent on timing.  I noticed it
> while running my SRFI-18 test suite in a loop, and it took hours to
> trigger.  Any suggestions?

I'm looking into this now.  Here's a nice little program that
reproduces the deadlock.

(use-modules (ice-9 threads))

(define other-thread
  (make-thread sleep 5))

(letrec ((delay-count 10)
	 (aproc (lambda ()
		  (display delay-count) (newline)
		  (set! delay-count (- delay-count 1))
		  (if (zero? delay-count)
		      (begin
			(display "sleeping...\n")
			(sleep 10)
			(display "waking...\n"))
		      (system-async-mark aproc)))))
  (sleep 2)
  (system-async-mark aproc)
  (join-thread other-thread))


Regards,
        Neil




  reply	other threads:[~2009-05-20 18:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-25  5:33 deadlock in scm_join_thread(_timed) Julian Graham
2008-05-25 13:16 ` Neil Jerram
2008-05-27  2:53   ` Julian Graham
2009-05-20 18:24     ` Neil Jerram [this message]
2009-05-20 20:58       ` Neil Jerram
2009-05-20 22:25         ` Ludovic Courtès
2009-05-23 22:57           ` Neil Jerram
2009-05-24 14:03             ` Ludovic Courtès
2009-05-24 21:26               ` Neil Jerram

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=87my97zl6u.fsf@arudy.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=joolean@gmail.com \
    /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).