GNU bug report logs - #27207
fsync on pipe output port exits without error message when input port has been closed

Previous Next

Package: guile;

Reported by: j kalbhenn <jkal <at> posteo.eu>

Date: Sat, 3 Jun 2017 11:11:01 UTC

Severity: normal

To reply to this bug, email your comments to 27207 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-guile <at> gnu.org:
bug#27207; Package guile. (Sat, 03 Jun 2017 11:11:01 GMT) Full text and rfc822 format available.
Acknowledgement sent to j kalbhenn <jkal <at> posteo.eu>:
New bug report received and forwarded. Copy sent to bug-guile <at> gnu.org. (Sat, 03 Jun 2017 11:11:02 GMT) Full text and rfc822 format available.

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

From: j kalbhenn <jkal <at> posteo.eu>
To: bug-guile <at> gnu.org
Subject: fsync on pipe output port exits without error message when input
 port has been closed
Date: Sat, 3 Jun 2017 11:10:33 +0000

tested with 2.2.2

(let*
  ( (ports (pipe))
    (in (car ports))
    (out (cdr ports)))
  (close in)
  (display 0 out)
  (display 1)
  (fsync out)
  (display 2))

without "(display 0 out)", error information is displayed and guile exits before "(display 2)".
with "(display 0 out)", no error information is displayed and guile exits before "(display 2)".
without "(close in)", error information is displayed in both cases.

i would expect the error information to be displayed in any case.
This bug report was last modified 8 years and 12 days ago.

Previous Next

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