GNU bug report logs - #15683
[critical] ERROR: ... close-pipe: pipe not in table

Previous Next

Package: guile;

Reported by: David Pirotte <david <at> altosw.be>

Date: Tue, 22 Oct 2013 16:26:02 UTC

Severity: important

Done: Mark H Weaver <mhw <at> netris.org>

Bug is archived. No further changes may be made.

Full log


Message #22 received at 15683 <at> debbugs.gnu.org (full text, mbox):

From: David Pirotte <david <at> altosw.be>
To: Mark H Weaver <mhw <at> netris.org>
Cc: 15683 <at> debbugs.gnu.org
Subject: Re: bug#15683: [critical] ERROR: ... close-pipe: pipe not in table
Date: Sun, 17 Nov 2013 15:54:23 -0200
Hello Mark,

Thank you for your work on this [tremendous] problem [for us].  I am running the
test on our 12 cores machine on the lab and so far so good [it did crash immediately
when running the 'old' guile...]

Not sure it interest you, but i made a module version of your test, where I
also call (current-processor-count), here below...

Many thanks again,
David

;; --

> To gain some confidence in these patches, I wrote a little test program:
> 

--8<---------------cut here---------------start------------->8---
(define-module (tests thread-safe-popen)
  :use-module (ice-9 popen)
  :export (thread-safe-popen-test))

(define (thread-safe-popen-test)
  (map (lambda (_)
         (call-with-new-thread
	  (lambda ()
	    (let loop ()
	      (let ((pipe (open-pipe* OPEN_READ "echo" "foo")))
		(read pipe)
		(close-pipe pipe))
	      (loop)))))
       (iota (current-processor-count))))

#!

(use-modules (tests thread-safe-popen))
(reload-module (resolve-module '(tests thread-safe-popen)))

(thread-safe-popen-test)

!#
--8<---------------cut here---------------end--------------->8---




This bug report was last modified 11 years and 181 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.