Re: busyloop in sigchld_handler

[Kim F. Storm]

Andreas Schwab <address@hidden> writes:

> address@hidden (Kim F. Storm) writes:
>
>> Andreas Schwab <address@hidden> writes:
>>
>>> address@hidden (Kim F. Storm) writes:
>>>
>>>> Why do we care about stopped processes?
>>>
>>> It is one of the possible states of a process, see process-status.  Any
>>> job control shell need to be able to handle that.
>>
>> Yes, but how does a stopped process cause a sigchld signal to be sent
>> to the parent?
>
> By not using SA_NOCLDSTOP when you register the handler.
>

Ah yes.

But the WUNTRACED flag doesn't mean we don't get info about
stopped processes, it means we also get info about stopped
ptrace'd processes:

                        switch (p->state) {
                        case TASK_STOPPED:
                                if (!p->exit_code)
                                        continue;
                                if (!(options & WUNTRACED) && !(p->ptrace & 
PT_PTRACED))
                                        continue;

But it's not relevant here, I guess.

-- 
Kim F. Storm <address@hidden> http://www.cua.dk