Ctrl+C kills applications that shouldn't be killed

[genki@…]

Hello devs,

When you start a bunch of apps like this: Pulse & Screen &

And then hit Ctrl+C in the terminal the apps will be killed. In BeOS this only works when you start the application without the "&".

[genki@…]

I reinitialized my partition, installed-haiku and the problem went away.

Something must have been wrong with the system. Sorry about that.

[axeld]

I'd rather reopen this bug. There is definitely something wrong with the scope of the signals sometimes, at least I observed this behaviour as well in the past.

[jackburton]

I found a very simple way to reproduce this:

• Open Terminal.
• Start "top" in the Terminal
• Hit CTRL-C.

Terminal closes as well. Only top should exit, right ?

[axeld]

Actually, those are different bugs. Originally, a control-C killed apps earlier started by the shell. That the Terminal is now closed then (you don't even have to run any app besides the shell in there) is a relatively young problem, probably be caused by the changes I made to the TTY driver.

[johndrinkwater]

Ctrl+C behaviour appears to have been fixed recently in hrev17338; just adding a note.

[korli]

the original problem (Ctrl+C kills backgrounds applications) seems fixed. the top problem described by Stefano remains.

[axeld]

Are you sure about that, J?r?me? I can't reproduce this anymore since the waitpid() fix.

[korli]

Axel, I tested this morning with rev17381 linux image on VPC: When I hit Ctrl+C while top is running, the Terminal is closed. And about the same behavior without Ctrl+C, running "which ps" also closes the Terminal.

[korli]

I deactivated a flag in revision 17431 which would cause bash to use sigsetjmp/ siglongjmp instead of setjmp/longjmp. At least on R5 it fixes the problem I had. I'll test on Haiku later. If the problem is fixed on Haiku as well, it would show a bug in our sigsetjmp/ siglongjmp implementation (see a new test app sigsetjmp_test.c).

[korli]

Ok, I tested on Haiku, and the bug is still here. sigsetjmp_test succeeds on Haiku as well. Moreover I tested with Dano bash binary and it behaves the same as ours. I reverted my change in bash config.h.

[nkoren@…]

I can confirm that this bug still exists, with an added twist -- once the terminal has been killed with a ctrl-C, it can't be reopened. This is happening with rev18509, running under Qemu.

[JamesB192]

A minor twist it seams that if you open a second window ctrl-c will not instantly kill off either terminal window. at least in build 18908.

[axeld]

Since I can only very rarely reproduce this, maybe Jérôme wants to own that bug for a while ;-)