From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Hang on CTRL-C (was Re: livelock on sigfe)
Date: Mon, 01 Apr 2013 05:03:00 -0000 [thread overview]
Message-ID: <20130401050302.GA5699@ednor.casa.cgf.cx> (raw)
In-Reply-To: <kjasrc$f1i$1@ger.gmane.org>
On Mon, Apr 01, 2013 at 11:53:38AM +0900, jojelino wrote:
>On 2013-03-17 AM 1:44, Christopher Faylor wrote:
>> No, not really. The caller in this case isn't interesting. The number
>> of threads executing is interesting.
>>
>> cgf
>>
>there is another debug session. I was trying to CTRL+C to mintty session
>in which make process was running. process hanged with livelock.
>
>After inspecting cygtls content, i found that the two thread have empty
>cygtls stack. so i couldn't figure out caller of _sigfe barrier, there
>is no opportunity to pop stack of thread 1(which is main thread trapped
>in sigfe wait loop), wait_sig thread or CTRL+C handler should have
>caused bizzare.
>GNU gdb (GDB) 7.5.50.20130309-cvs (cygwin-special)
>Copyright (C) 2013 Free Software Foundation, Inc.
>License GPLv3+: GNU GPL version 3 or later
><http://gnu.org/licenses/gpl.html>
>This is free software: you are free to change and redistribute it.
>There is NO WARRANTY, to the extent permitted by law. Type "show copying"
>and "show warranty" for details.
>This GDB was configured as "i686-cygwin".
>For bug reporting instructions, please see:
><http://www.gnu.org/software/gdb/bugs/>.
>
>warning: the current range check setting does not match the language.
>
>Whether backtraces should continue past the entry point of a program is off.
>Attaching to process 4516
>[New Thread 4516.0x1e88]
>[New Thread 4516.0x1310]
>[New Thread 4516.0xf74]
>Reading symbols from /usr/bin/clang.exe...(no debugging symbols
>found)...done.
>(gdb) i thr
> Id Target Id Frame
>* 3 Thread 4516.0xf74 0x7c95a22a in ntdll!DbgBreakPoint ()
> from /cygdrive/c/WINDOWS/system32/ntdll.dll
> 2 Thread 4516.0x1310 0x7c96845c in ntdll!KiFastSystemCallRet ()
> from /cygdrive/c/WINDOWS/system32/ntdll.dll
> 1 Thread 4516.0x1e88 0x7c96845c in ntdll!KiFastSystemCallRet ()
> from /cygdrive/c/WINDOWS/system32/ntdll.dll
>(gdb) i thr
> Id Target Id Frame
>* 3 Thread 4516.0xf74 0x7c95a22a in ntdll!DbgBreakPoint ()
> from /cygdrive/c/WINDOWS/system32/ntdll.dll
> 2 Thread 4516.0x1310 0x7c96845c in ntdll!KiFastSystemCallRet ()
> from /cygdrive/c/WINDOWS/system32/ntdll.dll
> 1 Thread 4516.0x1e88 0x7c96845c in ntdll!KiFastSystemCallRet ()
> from /cygdrive/c/WINDOWS/system32/ntdll.dll
Sorry for being so precise in my request that you provide information
on threads. It sure would be nice to see what thread 3 was doing via
a backtrace.
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-04-01 5:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 2:00 deadlock with busy waiting on sigfe 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
2013-03-16 16:44 ` Christopher Faylor
2013-04-01 2:54 ` livelock " jojelino
2013-04-01 5:03 ` Christopher Faylor [this message]
2013-04-01 18:23 ` Hang on CTRL-C (was Re: livelock on sigfe) 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=20130401050302.GA5699@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).