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


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

Re: bash signal during wait + read causes unkillable 100% CPU usage

Started byChet Ramey <chet.ramey@case.edu>
First post2018-09-17 10:42 -0400
Last post2018-09-17 10:42 -0400
Articles 1 — 1 participant

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: bash signal during wait + read causes unkillable 100% CPU usage Chet Ramey <chet.ramey@case.edu> - 2018-09-17 10:42 -0400

#14597 — Re: bash signal during wait + read causes unkillable 100% CPU usage

FromChet Ramey <chet.ramey@case.edu>
Date2018-09-17 10:42 -0400
SubjectRe: bash signal during wait + read causes unkillable 100% CPU usage
Message-ID<mailman.878.1537195370.1284.bug-bash@gnu.org>
On 9/16/18 11:47 PM, hackerb9@member.fsf.org wrote:

> Bash Version: 4.4
> Patch Level: 19
> Release Status: release
> 
> Description:
> 
> I was trying to work around the problem of bash not being able to
> cancel the read builtin command when a signal comes in and I stumbled
> upon this (perhaps unrelated) bug. I'm not sure exactly what's going
> on but I have a simple script that demonstrates the problem.

You should file a bug report with your distro and tell them to apply
bash-4.4 patch 21.

-- 
``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