X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.4 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Message-ID: <50C276AC.9090301@mailme.ath.cx> Date: Sat, 08 Dec 2012 00:07:24 +0100 From: bartels User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.11) Gecko/20121123 Icedove/10.0.11 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Intermittent failures retrieving process exit codes References: <50C2498C DOT 2000003 AT coverity DOT com> In-Reply-To: <50C2498C.2000003@coverity.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 12/07/2012 08:54 PM, Tom Honermann wrote: > > I recently was able to produce a very small test case that reproduces this issue reliably on some machines: Your suspicion about a race condition may very well be correct: I can easily confirm the problem on both iron and virtual smp, but not on a single core virtual. I have two instances of your test case running for half hour on the same core, without any problem: 30k cycles without hickup. Apart from the immediate effect exposed by your script, I have reason to believe that the root cause also affects other running (smp) processes. bartels -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple