From: Neil Jerram <neil@ossau.uklinux.net>
To: "Marijn Schouten (hkBst)" <hkBst@gentoo.org>
Cc: bug-guile@gnu.org, guile-devel@gnu.org
Subject: Re: popen test hangs
Date: Mon, 06 Jul 2009 19:25:40 +0100 [thread overview]
Message-ID: <87ab3hsm6z.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <4A51D4BA.3020905@gentoo.org> (Marijn Schouten's message of "Mon\, 06 Jul 2009 12\:40\:58 +0200")
"Marijn Schouten (hkBst)" <hkBst@gentoo.org> writes:
> it seems that the popen test hangs:
Grrr. I thought we'd nailed that...
> then it hangs for at least an hour or so. My configure invocation is:
>
> ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
> --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share
> --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64
> --disable-error-on-warning --disable-static --enable-posix --disable-networking
> --enable-regex --enable-deprecated --disable-elisp --enable-nls --disable-rpath
> --disable-debug-freelist --disable-debug-malloc --disable-guile-debug
> --with-threads --with-modules EMACS=no
>
> Any ideas what could be wrong or how to find out more?
Please look at the end of the check-guile.log file, to find out the
last test case that ran successfully, before the one that hung.
Then, if you like you could confirm that it is the next test that is
the problem, by removing everything all the other tests from
popen.test, and running just popen.test with
./pre-inst-guile -s test-suite/tests/popen.test
Then, if possible, add debugging (display ...) lines, use GDB, etc.,
to try to find out more about the hang.
Thanks!
Neil
next prev parent reply other threads:[~2009-07-06 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k52mn8kb.fsf@gnu.org>
2009-07-06 10:40 ` popen test hangs (was GNU Guile 1.8.7 released) Marijn Schouten (hkBst)
2009-07-06 18:25 ` Neil Jerram [this message]
2009-07-06 23:59 ` popen test hangs Marijn Schouten (hkBst)
2009-07-07 14:20 ` Marijn Schouten (hkBst)
2009-07-08 23:04 ` 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=87ab3hsm6z.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=bug-guile@gnu.org \
--cc=guile-devel@gnu.org \
--cc=hkBst@gentoo.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).