From: Mark H Weaver <mhw@netris.org>
To: David Pirotte <david@altosw.be>
Cc: 15683-done@debbugs.gnu.org
Subject: bug#15683: [critical] ERROR: ... close-pipe: pipe not in table
Date: Sat, 23 Nov 2013 18:07:56 -0500 [thread overview]
Message-ID: <87r4a6zpgz.fsf@netris.org> (raw)
In-Reply-To: <20131022142443.120865fb@capac> (David Pirotte's message of "Tue, 22 Oct 2013 14:24:43 -0200")
Hi David,
David Pirotte <david@altosw.be> writes:
> I am facing a bug that only occurs on extremely powerful servers:
>
> in ice-9/popen.scm:
> 106: 1 [close-pipe #<input: #{read pipe}# 69>]
> In unknown file:
> ?: 0 [scm-error misc-error #f "~A" ("close-pipe: pipe not in table") #f]
This bug should now be fixed on the stable-2.0 branch, which will become
Guile 2.0.10.
http://git.savannah.gnu.org/cgit/guile.git/commit/?h=stable-2.0&id=e7bd20f7d9b2110fdc0fa25db5a2bfe6b2214923
I'm closing this bug now.
Thanks!
Mark
prev parent reply other threads:[~2013-11-23 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 16:24 bug#15683: [critical] ERROR: ... close-pipe: pipe not in table David Pirotte
2013-11-17 9:46 ` Mark H Weaver
2013-11-17 10:04 ` Mark H Weaver
2013-11-17 11:29 ` Mark H Weaver
2013-11-17 15:59 ` Mark H Weaver
2013-11-17 17:54 ` David Pirotte
2013-11-23 23:07 ` Mark H Weaver [this message]
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=87r4a6zpgz.fsf@netris.org \
--to=mhw@netris.org \
--cc=15683-done@debbugs.gnu.org \
--cc=david@altosw.be \
/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).