From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: deadlock with busy waiting on sigfe
Date: Wed, 16 Jan 2013 01:47:00 -0000 [thread overview]
Message-ID: <20130116014646.GB13175@ednor.casa.cgf.cx> (raw)
In-Reply-To: <kd2d69$lam$1@ger.gmane.org>
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.
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
next prev parent reply other threads:[~2013-01-16 1:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 2:00 jojelino
2013-01-16 1:47 ` Christopher Faylor [this message]
2013-01-16 2:14 ` Christopher Faylor
2013-01-20 5:23 ` jojelino
2013-01-20 6:55 ` Christopher Faylor
2013-03-11 8:54 ` jojelino
2013-03-11 14:36 ` Christopher Faylor
2013-03-11 19:36 ` jojelino
2013-03-11 19:50 ` jojelino
2013-03-11 20:46 ` Christopher Faylor
2013-03-15 19:41 ` Christopher Faylor
2013-03-16 1:46 ` jojelino
2013-03-16 2:00 ` jojelino
2013-03-16 16:44 ` Christopher Faylor
2013-04-01 2:54 ` livelock " jojelino
2013-04-01 5:03 ` Hang on CTRL-C (was Re: livelock on sigfe) Christopher Faylor
2013-04-01 18:23 ` jojelino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130116014646.GB13175@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).