From: j kalbhenn <jkal@posteo.eu>
To: 27207@debbugs.gnu.org
Subject: bug#27207: fsync on pipe output port exits without error message when input port has been closed
Date: Sat, 3 Jun 2017 11:10:33 +0000 [thread overview]
Message-ID: <20170603111032.GA22207@sph-desktop.fritz.box> (raw)
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.
reply other threads:[~2017-06-03 11:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170603111032.GA22207@sph-desktop.fritz.box \
--to=jkal@posteo.eu \
--cc=27207@debbugs.gnu.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).