Re: busyloop in sigchld_handler

[David Kastrup]

Andreas Schwab <address@hidden> writes:

> David Kastrup <address@hidden> writes:
>
>> The CPU is claimed by the process with the loop, so no other process
>> may actually progress to a state which can be "wait"ed for.
>
> Of there is no child to be waited for then there is no loop.

In order to make sophistics solve the problem, you need to convince
the kernel.

-- 
David Kastrup