This is the mail archive of the
libc-alpha@sourceware.cygnus.com
mailing list for the glibc project.
Re: [Keith Owens <kaos@ocs.com.au>] libc/1174: stdio without SA_RESTART loses output
- To: libc-alpha Mailinglist <libc-alpha@sourceware.cygnus.com>
- Subject: Re: [Keith Owens <kaos@ocs.com.au>] libc/1174: stdio without SA_RESTART loses output
- From: Ulrich Drepper <drepper@cygnus.com>
- Date: 25 Jun 1999 15:48:11 -0700
- Cc: Keith Owens <kaos@ocs.com.au>
- References: <u8vhccci19.fsf@arthur.rhein-neckar.de>
- Reply-To: drepper@cygnus.com (Ulrich Drepper)
Andreas Jaeger <aj@arthur.rhein-neckar.de> writes:
> [1 <text/plain>]
>
> Here comes another bug report - this time the problem is signal
> handling.
>
> The program writes blocks of 512 data to stdout and loses 8 such
> blocks when a signal occurs. If the program use write in a loop, it
> should work with checking errno for EINTR - but the program uses
> fwrite.
>
> What needs to be done?
I don't think anything but I have to verify this. The code causing
this behaviour was introduced because of a POSIX conformance
test. This required that it is possible to interrupt a blocking fwrite
using a signal (e.g., SIGALRM).
I'll have to look at this in more detail and therefore haven"t
responded so far.
--
---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------