From: jojelino <jojelino@gmail.com>
To: cygwin@cygwin.com
Subject: Re: deadlock with busy waiting on sigfe
Date: Sat, 16 Mar 2013 02:00:00 -0000 [thread overview]
Message-ID: <ki0jn6$5pl$1@ger.gmane.org> (raw)
In-Reply-To: <ki0isq$ts8$1@ger.gmane.org>
On 2013-03-16 AM 10:46, jojelino wrote:
> On 2013-03-16 AM 4:41, Christopher Faylor wrote:
>> On Mon, Mar 11, 2013 at 04:45:54PM -0400, Christopher Faylor wrote:
>> Actually, if you are running this on a DOS console, and you hit CTRL-C,
>> you will have at least one other thread executing.
>>
>> Were you running this under mintty (aka a pty) or in a Windows cmd
>> shell?
>>
>> cgf
>>
> It was mintty i was running. and shell command was
> for i in `seq 10000`;do ./hop.py list.txt ;done
And it would take at least another month to reproduce the busy wait.
I forgot to print cygtls::stackptr[-1] at that time. which would be key
to identify the cause of the problem.
--
Regards.
--
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-03-16 2:00 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
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 [this message]
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='ki0jn6$5pl$1@ger.gmane.org' \
--to=jojelino@gmail.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).