Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #14940 > unrolled thread

Re: write() not retried after EINTR in printf and echo

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: write() not retried after EINTR in printf and echo Chet Ramey <chet.ramey@case.edu> - 2018-12-21 14:57 -0500

#14940 — Re: write() not retried after EINTR in printf and echo

On 12/19/18 10:15 PM, Bize Ma wrote:
> Chet Ramey (<chet.ramey@case.edu <mailto:chet.ramey@case.edu>>) wrote:
> 
>     And yet, when you look at the source, the signal handlers are installed
>     with SA_RESTART. For example,
> 
>  
> 
>     #  if defined (SIGWINCH)
>       act.sa_flags = (sig == SIGWINCH) ? SA_RESTART : 0;
>     #  else
>       act.sa_flags = 0;
>     #  endif /* SIGWINCH */
> 
>     in lib/readline/signals.c:rl_set_sighandler().
> 
> 
> True for SIGWINCH, but "write error: Interrupted system call"
> is still exposed to users (which it shouldn't) for other signals:

Ah, now we're moving the goalposts. There's a case to be made for doing
that, I suppose, but I'd rather defer to the system's default handling
for a particular signal.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web