Re: [BUG] Bash not reacting to Ctrl-C

2011-02-09 Thread Oleg Nesterov
On 02/08, Chet Ramey wrote: > > On 2/8/11 4:17 PM, Oleg Nesterov wrote: > > > Once again. If bash gets ^C and at the same time the current foreground > > child exits normally (either because this jctl signal races with exit() > > or because the child hooks SIGINT and exits after that) SIGINT is los

Re: [BUG] Bash not reacting to Ctrl-C

2011-02-09 Thread Oleg Nesterov
On 02/08, Chet Ramey wrote: > > On 2/8/11 7:11 PM, Ingo Molnar wrote: > > > > Oleg also found another simple testcase i think - and Thomas (Cc:-ed) > > reported > > similar Ctrl-C problems with Bash as well. > > I tried to reproduce it and wasn't able to. I use Mac OS X. Strange, but I know noth

Re: [BUG] Bash not reacting to Ctrl-C

2011-02-09 Thread Ingo Molnar
* Oleg Nesterov wrote: > That is why I provided another test-case, let me repeat it: > > #!./bash > > perl -we '$SIG{INT} = sub {exit}; sleep' > > echo "Hehe, I am going to sleep after ^C" > sleep 100 This reliably reproduces the (formerly sporadic) script Ctrl-C bug

miscompilation at gcc -O2

2011-02-09 Thread Eric Blake
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu' -DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale' -

Re: [BUG] Bash not reacting to Ctrl-C

2011-02-09 Thread Bob Proulx
Oleg Nesterov wrote: > Bob Proulx wrote: > > Is the behavior you observe any different for this case? > > $ bash -c 'while true; do /bin/true || exit 1; done' > > Or different for this case? > > $ bash -e -c 'while true; do /bin/true; done' > > The same. I expected that to behave differently

Re: [BUG] Bash not reacting to Ctrl-C

2011-02-09 Thread Bob Proulx
Ingo Molnar wrote: > Could you try the reproducer please? > > Once you run it, try to stop it via Ctrl-C, and try to do this a > couple of times. I was not able to reproduce your problem using your (I believe to be slightly incorrect) test case: bash -c 'while true; do /bin/true; done' It was

Re: [BUG] Bash not reacting to Ctrl-C

2011-02-09 Thread Bob Proulx
Oleg Nesterov wrote: > That is why I provided another test-case, let me repeat it: Sorry but I missed seeing that the first time through or I would have commented. > #!./bash > perl -we '$SIG{INT} = sub {exit}; sleep' > echo "Hehe, I am going to sleep after ^C" > sleep 100

Re: [BUG] Bash not reacting to Ctrl-C

2011-02-09 Thread Oleg Nesterov
On 02/09, Bob Proulx wrote: > > Oleg Nesterov wrote: > > Bob Proulx wrote: > > > Is the behavior you observe any different for this case? > > > $ bash -c 'while true; do /bin/true || exit 1; done' > > > Or different for this case? > > > $ bash -e -c 'while true; do /bin/true; done' > > > > The

Re: [BUG] Bash not reacting to Ctrl-C

2011-02-09 Thread Oleg Nesterov
On 02/09, Bob Proulx wrote: > > Ingo Molnar wrote: > > Could you try the reproducer please? > > > > Once you run it, try to stop it via Ctrl-C, and try to do this a > > couple of times. > > I was not able to reproduce your problem using your (I believe to be > slightly incorrect) test case: > > b

Re: [BUG] Bash not reacting to Ctrl-C

2011-02-09 Thread Oleg Nesterov
On 02/09, Bob Proulx wrote: > > Oleg Nesterov wrote: > > > That is why I provided another test-case, let me repeat it: > > Sorry but I missed seeing that the first time through or I would have > commented. > > > #!./bash > > perl -we '$SIG{INT} = sub {exit}; sleep' > > echo "Hehe, I am

Re: miscompilation at gcc -O2

2011-02-09 Thread Jon Seymour
Good catch - how long did that take to find? jon. On Thu, Feb 10, 2011 at 6:06 AM, Eric Blake wrote: > Configuration Information [Automatically generated, do not change]: > Machine: x86_64 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' > -DCONF_O