From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: 1.8 make check failing in popen.test
Date: Thu, 17 Aug 2006 20:01:30 -0700 [thread overview]
Message-ID: <87bqqieohh.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <87mza4uurn.fsf@zip.com.au> (Kevin Ryde's message of "Thu, 17 Aug 2006 09:26:52 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> I guess a select hang is probably the read-char waiting for the
> child to signal to the parent that it (the child) has closed stdout
> so the parent can go ahead and test that connection (for eof).
> Maybe gdb or some printfs can show if that's so.
I haven't had a chance to investigate much further yet, but if I run
make check under gdb and hit Ctrl-C while popen.test is hung, there
are two threads that were running. The first thread's backtrace looks
like this:
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x40281f41 in select () from /lib/tls/i686/cmov/libc.so.6
#2 0x400b481c in scm_std_select (nfds=29, readfds=0xbfa8621c, writefds=0x0,
exceptfds=0x0, timeout=0x0) at threads.c:1363
#3 0x4005f8ce in fport_fill_input (port=0x40647400) at fports.c:550
#4 0x40086aff in scm_fill_input (port=0x40647400) at ports.c:973
#5 0x40086c40 in scm_getc (port=0x40647400) at ports.c:991
#6 0x40088d7d in scm_read_char (port=0x0) at ports.c:948
#7 0x4005ad54 in ceval (x=0x404, env=0x40647188) at eval.c:4218
and the second thread's backtrace looks like this:
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x401b681b in __read_nocancel () from /lib/tls/i686/cmov/libpthread.so.0
#2 0x40091923 in do_read_without_guile (raw_data=0x40b310d8) at scmsigs.c:134
#3 0x400b42fc in scm_without_guile (func=0x400918f0 <do_read_without_guile>,
data=0x40b310d8) at threads.c:657
#4 0x40091875 in signal_delivery_thread (data=0x0) at scmsigs.c:145
#5 0x400b67b5 in scm_c_catch (tag=0x104,
body=0x400917f0 <signal_delivery_thread>, body_data=0x0,
handler=0x400b6080 <scm_handle_by_message>, handler_data=0x400d867e,
pre_unwind_handler=0, pre_unwind_handler_data=0x0) at throw.c:204
#6 0x400b69c5 in scm_internal_catch (tag=0x104,
body=0x400917f0 <signal_delivery_thread>, body_data=0x0,
handler=0x400b6080 <scm_handle_by_message>, handler_data=0x400d867e)
at throw.c:218
#7 0x400b55ad in really_spawn (d=0xbfa860c8) at threads.c:777
--
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-08-18 3:01 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 [this message]
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
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=87bqqieohh.fsf@raven.defaultvalue.org \
--to=rlb@defaultvalue.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).