X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,TW_GJ X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4DA6EEF2.5050908@ece.cmu.edu> References: <4DA6EEF2 DOT 5050908 AT ece DOT cmu DOT edu> Date: Thu, 14 Apr 2011 15:19:17 -0700 Message-ID: Subject: Re: bash died waiting for longjmp before initialization From: Lonni J Friedman To: Ryan Johnson Cc: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Hi Ryan, Thanks for your reply. I have to admit, I had never heard of the concept of a rebase until you mentioned it. After googling, it sounds like this is what I should try? http://www.heikkitoivonen.net/blog/2008/11/26/cygwin-upgrades-and-rebaseall/ If so, I guess I can give that a try on one system and see if it helps. I'll also try out your attacked testcase and provide feedback. thanks On Thu, Apr 14, 2011 at 5:56 AM, Ryan Johnson wrote: > I haven't had bash crash on me, but I do get other fork-related errors on= my > win7-x64 system. You might try running the attached testcase (make && > ./fork) a few times to see if it reproduces the problem. > > For me it usually complains about access violations during the fork and > sometimes dies waiting for longjmp, with the culprit being two dlls which > want to load at the same address. > > The usual advice most likely applies: rebase your system (a workaround wh= ich > usually prevents the condition that triggers the bug... until you run > setup.exe again). > > Regards, > Ryan > > On 2:59 PM, Lonni J Friedman wrote: >> >> Greetings, >> I've been experiencing seemingly random bash shell crashes on all >> (20+) Windows7-x64 systems that I have in a lab which are used for >> automated tests of my employer's software. =C2=A0Every time that bash >> crashes, I see an error very similar to the following: >> 5 [main] bash 3100 fork: child -1 - died waiting for longjmp before >> initialization, retry -1, exit code 0xC0000142, errno 11 >> >> Occasionally, I also see a few additional errors immediately after the >> above error, such as these: >> =C2=A0 =C2=A0 =C2=A0 2 [main] ? (4264) child_copy: cygheap read copy fai= led, >> 0x611688E0..0x6116BCF8, done 0, windows pid 0, Win32 error 299 >> =C2=A0124115 [main] bash 4264 child_copy: dll data read copy failed, >> 0x61102000..0x61106BA0, done 0, windows pid 4264, Win32 error 299 >> >> I've not had any success manually reproducing or attempting to force >> this crash. =C2=A0Its always been completely random, however it happens = at >> least once every day on every Win7-x64 system. >> >> I've attached the output from running 'cygcheck -s -v -r' on one of >> the systems where this failure has occurred many times. =C2=A0I can prov= ide >> the output from other systems as well if requested. >> >> I'd be happy to answer any questions or provide more information, or >> perform some form of debugging if someone requests something specific. >> >> thanks! > > --=20 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 netllama AT gma= il.com LlamaLand=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0=C2=A0 https://netllama.linux-sxs.org -- 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