public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/29459] fwrite does not return EPIPE when underlying write fails with EPIPE.
Date: Mon, 08 Aug 2022 19:19:11 +0000 [thread overview]
Message-ID: <bug-29459-131-iVhWTPra1t@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29459-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29459
--- Comment #4 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Andreas Schwab from comment #3)
> How exactly is the test program called?
./fwrite -l hello 5000 | head -n1
Such that head terminates and closes the pipe after reading one line.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-08 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 17:32 [Bug stdio/29459] New: " carlos at redhat dot com
2022-08-08 17:33 ` [Bug stdio/29459] " carlos at redhat dot com
2022-08-08 17:33 ` carlos at redhat dot com
2022-08-08 17:35 ` carlos at redhat dot com
2022-08-08 17:50 ` schwab@linux-m68k.org
2022-08-08 19:19 ` carlos at redhat dot com [this message]
2022-08-08 19:57 ` sam at gentoo dot org
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-29459-131-iVhWTPra1t@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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).