X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 12 Mar 2010 17:27:36 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Cygwin 1.7: Concurrency Issue with Shared State Initialization Message-ID: <20100312162736.GS6505@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) 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 On Mar 12 16:48, Schmidt, Oliver wrote: > 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, > 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 > 7D6373D8 jne 7D628061 > 7D6373DE lea eax,[ebp-28h] > 7D6373E1 push eax > 7D6373E2 push ebx > 7D6373E3 call 7D61CCB1 > 7D6373E8 cmp eax,ebx > 7D6373EA jge 7D6373D2 What about building the Cygwin DLL with debug symbols and using the GDB debugger instead of MSVC? The latter doesn't grok the Dwarf-2 debugging format. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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