Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #11512
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: SIGINT handling |
| Date | 2015-09-19 21:28 -0400 |
| Organization | ITS, Case Western Reserve University |
| Message-ID | <mailman.1424.1442712513.19560.bug-bash@gnu.org> (permalink) |
| References | <20150918151439.GA16455@chaz.gmail.com> <55FDC8B4.4000505@case.edu> <20150919213101.GA4393@chaz.gmail.com> |
On 9/19/15 5:31 PM, Stephane Chazelas wrote: > 2015-09-19 16:42:28 -0400, Chet Ramey: > [...] >> I'm surprised you've managed to avoid the dozen or so discussions on the >> topic. >> >> http://lists.gnu.org/archive/html/bug-bash/2014-03/msg00108.html > [...] > > Thanks for the links. I still think the comments on the second > article I sent > (http://thread.gmane.org/gmane.comp.shells.bash.bugs/24178/focus=24183) > still hold though and from a quick read I don't see those points > being mentioned in the past discussions (but that was a quick > read). > > I notice that you mention the race conditions have been fixed, > but I'm still seeing some non-deterministic behaviour. I can't reproduce this on Mac OS X and RHEL 6 and 7, the systems I have readily available today. The shell notes when it sees SIGINT and whether or not waitpid returns -1/EINTR. If the sleep exits due to SIGINT, even after the waitpid returns -1, the shell assumes it didn't catch and handle the SIGINT and the shell calls the trap handler. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
Back to gnu.bash.bug | Previous | Next | Find similar
Re: SIGINT handling Chet Ramey <chet.ramey@case.edu> - 2015-09-19 21:28 -0400
csiph-web