Bug report: two 'kills' kill the shell

On MP linux 2.3.47 for ia64 running on a 4-processor system, with this program:

main()

{
        while(1)
        {
                sleep(2);
                printf("Hello world\n");
        }
}

I started up 4 of them in background from one shell. Then went to another window and started killing them with the 'kill' command (not kill 9, just plain kill). The second 'kill' kills the shell, consistently. It looks like maybe the shell can handle one SIGCHILD but not two of them.

David Robboy

David> I started up 4 of them in background from one shell. Then went David> to another window and started killing them with the 'kill' David> command (not kill 9, just plain kill). The second 'kill' kills David> the shell, consistently. It looks like maybe the shell can David> handle one SIGCHILD but not two of them.

There are some problems with the signal handling in the current kernels, I suspect thats what you're seeing.

Jes

I can't reproduce this on 2.3.99-pre5 (SMP). Please try the latest kernel. There was a fix to asynchronous signal delivery in the 2.3.51 patches.

	--david

David> On MP linux 2.3.47 for ia64 running on a 4-processor system, David> with this program:

David> main() { while(1) { sleep(2); printf("Hello world\n"); } }

David> I started up 4 of them in background from one shell. Then David> went to another window and started killing them with the David> 'kill' command (not kill 9, just plain kill). The second David> 'kill' kills the shell, consistently. It looks like maybe David> the shell can handle one SIGCHILD but not two of them.

David> David Robboy

David> _______________________________________________ Linux-IA64 David> mailing list [email protected]
David> http://lists.linuxia64.org/lists/listinfo/linux-ia64