Re: "tcsetattr: Interrupted system call" after rapid-fire ^C chars

[Chet Ramey]

Joe Peterson wrote:

>         Well, without a hacked kernel, you'll probably not hit
>         *this* manifestation of the issue, but what I did was:
> 
>         - run a text processing program (like "cat" or "tr")
>         - hit ctrl-S
>         - enter lots of text that will then produce lots of output
>         - hold down ctrl-C until the error is produced
> 
> Fix:
>         Should interrupts be trapped during call to tcsetattr()?

I don't think so.  Readline already blocks interrupts when it calls
tcsetattr, and bash handles that call returning -1/EINTR appropriately.

Chet


-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer

Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/