Path: csiph.com!xmission!news.glorb.com!usenet.stanford.edu!not-for-mail From: Chet Ramey Newsgroups: gnu.bash.bug Subject: Re: SIGINT handling Date: Wed, 23 Sep 2015 21:27:00 -0400 Organization: ITS, Case Western Reserve University Lines: 33 Approved: bug-bash@gnu.org Message-ID: References: <20150918151439.GA16455@chaz.gmail.com> <55FDC8B4.4000505@case.edu> <20150919213101.GA4393@chaz.gmail.com> Reply-To: chet.ramey@case.edu NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Trace: usenet.stanford.edu 1443058033 12565 208.118.235.17 (24 Sep 2015 01:27:13 GMT) X-Complaints-To: action@cs.stanford.edu Cc: bug-bash , chet.ramey@case.edu To: Stephane Chazelas Envelope-to: bug-bash@gnu.org User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 In-Reply-To: <20150919213101.GA4393@chaz.gmail.com> X-Junkmail-Whitelist: YES (by domain whitelist at mpv2.tis.cwru.edu) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 129.22.105.37 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.bash.bug:11551 On 9/19/15 5:31 PM, Stephane Chazelas wrote: > In case it was caused by some Debian patch, I recompiled the > code of 4.3.42 from gnu.org and the one from the devel branch on > the git repository (commit bash-20150911 snapshot) and still: > > $ ./bash -c 'sh -c "trap exit INT; sleep 10; :"; echo hi' > ^Chi > $ ./bash -c 'sh -c "trap exit INT; sleep 10; :"; echo hi' > ^Chi > $ ./bash -c 'sh -c "trap exit INT; sleep 10; :"; echo hi' > ^C > $ ./bash -c 'sh -c "trap exit INT; sleep 10; :"; echo hi' > ^Chi > > Sometimes (and the frequency of occurrences is erratic, > generally roughly 80% of "hi"s but at times, I don't see a "hi" > in a while), the "hi" doesn't show up. Note that I press ^C well > after sleep has started. It would be nice to see a system call trace for this so we can check what's going on with the timing. Can you reproduce this on anything other than Debian? I'm wondering whether it's a Linux-4 kernel phenomenon. Plus I don't have any Debian machines laying around. Chet -- ``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/