X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-system-of-record:x-gm-message-state; bh=8/lwybkId+0rcYGzXRsMcB9sNCAXFG+jssQENY0qHPI=; b=CerkxMaYVoc3NIyK8Xeg8pzwsWh1CQK24BYli90b/2VogCYO4Tui9iDzvoNwUAd58t Bcw2D1ne3VxzILtx0wBpdIIYW4E+/RDQCk41ATbHF3LFg2usHdKmzTHkysQVeC2Wkp+E Hpj956x5+NRFAttZEmue6IvRDtA658RuYTYrZWznyo7kMt11n2fFCMbHGG35NbL9IlWx vi/HckDkUna4Kt0Qyyf4u6WvXmCIG2dt2T90CjLyR95FEjEHClemP7Nd95C3yOh2GioA z6WPYN3M68TLGRUf6iM8AHKUQiI+pk5h0NhTNp6HTWTfmt707blSuyFdRBMd76sNeV7F TBjg== MIME-Version: 1.0 Date: Tue, 7 Aug 2012 14:59:56 +0400 Message-ID: Subject: Re: Race condition that leads to random crashes in cygwin-based builds. From: Andrey Khalyavin To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-System-Of-Record: true X-Gm-Message-State: ALoCoQmzUZ2XYD2BAFJIN58W+EBpzDlCBqmD2W5ZGCZ4D1K9BRYg04nFP7v5tlSYcOyBtaGTzSW44Vpg+fKKZwLPSlJnVo1ZKhLOl/9YgQQavFgS/5oNz4xjGaViTInvR3l0+hnTl7QrZx+rqk5/2dCTIvX9tJkVoQeCx0gp7ASkyhynGwvGGW5CIvmxxQtwQeJCXiWq58vE 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 Aug 7 Corinna Vinschen wrote: >On Aug 6 19:31, Andrey Khalyavin wrote: >> 2012/8/6 Corinna Vinschen wrote: >> > Andrey? >> > >> > On Jul 24 15:57, Corinna Vinschen wrote: >> >> On Jul 24 17:25, Andrey Khalyavin wrote: >> >> > Hi, we have build bots that crash randomly on Windows XP and rarely on >> >> > Windows 7. >> >> > [...] >> >> > 5. Task switching happens and first process proceeds to execute >> >> > GetVersionEx with >> >> > version cleared by memset and so not having its size set. >> >> > 6. GetVersionEx returns error and first process fails to start. >> >> > >> >> > If there is no easy way to add synchronization to wincapc::init, I >> >> > suggest to make >> >> > wincap a regular (not shared) variable. >> >> >> >> There's another way, afaics. The idea here was that wincap is only >> >> ever set once, and even *if* the information is written twice, the >> >> content will be identical. >> >> >> >> So, afaics, the above problem is a result of using memset at all. At >> >> startup, wincap is all 0 anyway, so the memset is not required and >> >> apparently it even hurts. Weird that nobody saw this problem before. >> >> >> >> I applied a patch which should fix this problem. Please give the >> >> next developer snapshot from http://cygwin.com/snapshots/ a try, >> >> or build yourself from CVS. >> > >> > Ping? Any feedback? Did you ever try a snapshot? >> >> I updated our cygwin with core libraries from 20120725 snapshot. There >> are still crashes in our build, I'm investigating them. Haven't got a >> crash dump yet. This time I have to catch them on the bots instead of >> local computer. > >Please use the *latest* snapshot from CVS, 20120803. There were other >potential reasons for crashes which only have been (tried to) fix in >the latest snapshot. Thank you. I will update cygwin before I do a new step in investigating our build issues (need to implement some way to get crash dumps on bots). Andrey Khalyavin. -- 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