X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-10.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI X-Spam-Check-By: sourceware.org From: "Schmidt, Oliver" To: "cygwin AT cygwin DOT com" Date: Fri, 12 Mar 2010 16:48:14 +0100 Subject: Re: Cygwin 1.7: Concurrency Issue with Shared State Initialization Message-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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 Hi, > Does the patch help? As the issue is sporadic it's not that easy to come up with a conclusive answer... I downloaded http://cygwin.com/snapshots/cygwin1-20100309.dll.bz2,=20 unpacked and renamed the DLL and used it as drop-in replacement to the 1.7.1 DLL. I experienced three times by now the effect that echo.exe "hangs" without using significant CPU time. Attaching a MSVC debugger I could only find out that in all three cases the executable stays in this endless loop: 7D6373D2 cmp dword ptr ds:[7D6A0220h],edi=20 7D6373D8 jne 7D628061=20 7D6373DE lea eax,[ebp-28h]=20 7D6373E1 push eax=20=20 7D6373E2 push ebx=20=20 7D6373E3 call 7D61CCB1=20 7D6373E8 cmp eax,ebx=20 7D6373EA jge 7D6373D2=20 I'm sort of reluctant to present this information this way as I'm afraid I'm to give someone a bum steer. However I haven't had this effect so far with with the 1.7.1 DLL so it would be at least one possible explanation that the patch has a bug showing up in the very sporadic case it is supposed to fix. Regards, Oliver -- 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