[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: deadlock in waitchld()

From: Chet Ramey
Subject: Re: deadlock in waitchld()
Date: Fri, 24 May 2013 10:00:34 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5

On 5/24/13 9:30 AM, Roman Rakus wrote:
> The race is in do-while loop in wait_for(). At the start of wait_for() we
> are blocking SIGCHLD, however echo process ends during the loop and we
> don't register it (don't handle SIGCHLD, which is sent).
> Looking at the code, there is MUST_UNBLOCK_CHLD. May it make any harm to
> enable it by default?

I spent a lot of time looking at this yesterday, and I have it pretty much
fixed.  The problem is in the trap handling code, not wait_for().  The trap
problem ends up corrupting the jobs data structure, which is why wait_for


``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]