All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: julie Sullivan <kernelmail.jms@gmail.com>
Cc: linux-kernel@vger.kernel.org, "Tejun Heo" <tj@kernel.org>,
	roland@redhat.com, jan.kratochvil@redhat.com,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>
Subject: Re: Bash not reacting to Ctrl-C
Date: Sat, 29 Jan 2011 11:37:03 +0100	[thread overview]
Message-ID: <20110129103703.GA13189@elte.hu> (raw)
In-Reply-To: <AANLkTimKhrCvyzmGsogxWUOsgiek1vnQ17Tjnhm0T=LM@mail.gmail.com>


* julie Sullivan <kernelmail.jms@gmail.com> wrote:

> (apologies for not replying to original thread, I wasn't subscribed)
> 
> >Might be some Bash assumption or race that works under other OSs but somehow Linux
> >does differently. IIRC Bash is being developed on MacOS-X.
> 
> Yep, and I can confirm that this behaviour is the same on MacOS-X too
> (I tested Ingo's
> bash scripts in my break on a machine at work today).
> Ctrl-C is lost about once in every 10 times.

Ok, so it's likely a Bash bug.

[ It's annoying nevertheless :) ]

> >See that '^C^C' line? That is where i had to do Ctrl-C twice.
> 
> I beat Ingo - I got three '^C's in a row on the Mac a couple of times :-)

:-)

Thanks,

	Ingo

  reply	other threads:[~2011-01-29 10:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28 22:44 Bash not reacting to Ctrl-C julie Sullivan
2011-01-29 10:37 ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-01-28 15:08 [PATCHSET] ptrace,signal: group stop / ptrace updates Tejun Heo
2011-01-28 16:54 ` Ingo Molnar
2011-01-28 17:55   ` Oleg Nesterov
2011-01-28 18:29     ` Bash not reacting to Ctrl-C Ingo Molnar
2011-02-05 20:34       ` Oleg Nesterov
2011-02-07 13:08         ` Oleg Nesterov
2011-02-09  6:17           ` Michael Witten
2011-02-09 14:53             ` Ingo Molnar
2011-02-09 19:37               ` Michael Witten
2011-02-11 14:41           ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110129103703.GA13189@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=jan.kratochvil@redhat.com \
    --cc=kernelmail.jms@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.