From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: 1.8 make check failing in popen.test
Date: Sun, 10 Sep 2006 09:24:51 -0700 [thread overview]
Message-ID: <87zmd7sn8s.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <87irjxvvsw.fsf@raven.defaultvalue.org> (Rob Browning's message of "Sat, 09 Sep 2006 09:39:27 -0700")
Rob Browning <rlb@defaultvalue.org> writes:
> In any case, I'll see if I can still get it to hang using
> --without-threads.
I have a tree here where I added a (gc) call before and after the
port-for-each call in popen.scm (in the child). Given that and
--with-threads=yes, "make check" would hang every time I ran it.
I rebuilt that tree with --with-threads=no and I ran make check
repeatedly. After 20 iterations, it hadn't blocked.
So I removed the (gc) calls and rebuilt with --with-threads=yes, and
make check blocked after 7 iterations and then 183 iterations.
Though not conclusive, these results, when combined with the gdb
backtrace I posted earlier showing the blockage in scm_gc() while
trying to lock a a mutex, seem to suggest that the remaining problem
is thread related.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-09-10 16:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-23 8:37 1.8 make check failing in popen.test Rob Browning
2006-07-23 22:36 ` Kevin Ryde
2006-07-23 23:12 ` Rob Browning
2006-07-24 7:25 ` Ludovic Courtès
2006-07-30 1:59 ` Rob Browning
2006-08-15 8:35 ` Rob Browning
2006-08-15 23:13 ` Kevin Ryde
2006-08-16 1:18 ` Rob Browning
2006-08-16 23:26 ` Kevin Ryde
2006-08-18 3:01 ` Rob Browning
2006-08-21 23:38 ` Kevin Ryde
2006-08-22 2:03 ` Rob Browning
2006-08-25 1:16 ` Kevin Ryde
2006-08-25 2:39 ` Rob Browning
2006-08-27 20:06 ` Rob Browning
2006-08-27 20:22 ` Rob Browning
2006-08-30 7:50 ` Rob Browning
2006-08-31 0:24 ` Kevin Ryde
2006-08-31 6:28 ` Rob Browning
2006-09-04 2:45 ` Rob Browning
2006-09-07 20:46 ` Kevin Ryde
2006-09-08 2:45 ` Rob Browning
2006-09-08 23:05 ` Kevin Ryde
2006-09-09 12:52 ` Marius Vollmer
2006-09-09 16:39 ` Rob Browning
2006-09-10 16:24 ` Rob Browning [this message]
2006-09-11 1:16 ` Rob Browning
2006-09-11 6:40 ` Neil Jerram
2006-09-11 15:57 ` Rob Browning
2006-09-11 17:40 ` 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=87zmd7sn8s.fsf@raven.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@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).