X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18Fnut38B8WDgJtzeUKKPe/ Date: Tue, 15 Jan 2013 21:14:14 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: deadlock with busy waiting on sigfe Message-ID: <20130116021414.GA14341@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20130116014646 DOT GB13175 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130116014646.GB13175@ednor.casa.cgf.cx> 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 Tue, Jan 15, 2013 at 08:46:46PM -0500, Christopher Faylor wrote: >On Tue, Jan 15, 2013 at 11:00:16AM +0900, jojelino wrote: >>Caused by executing following command and ctrl+c to interrupt in bash shell. >>sh -c "cd /tmp/openjpeg/src/bin/jp2 && /usr/bin/i686-pc-mingw32-gcc.exe >> -DOPJ_EXPORTS -ffast-math -O3 -DNDEBUG >>@CMakeFiles/opj_compress.dir/includes_C.rsp -o >>CMakeFiles/opj_compress.dir/convert.c.obj -c >>/tmp/openjpeg/src/bin/jp2/convert.c" >> >>SleepEx is being spammed across threads. some thread got tls lock but >>didn't released it. >>how can i fix the problem? > >Sorry but there is no useful information here. > >How about providing some basic details like: > >1) What version of Cygwin you're running. > >2) A reproducer that doesn't involve downloading a large package and >(apparently) running configure. > >? > >You can also forgo the gdb backtraces. It is almost never useful to >include those in a bug report. Sorry, the backtraces were actually useful because they show that you are apparently running cygwin-snapshot-20130107. Apparently you haven't been watching the discussion about this issue in the Cygwin list. The problem of a Cygwin process hanging after a single CTRL-C should be fixed in later snapshots although there is another reported CTRL-C issue. cgf -- 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