X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=ES3ncV7J4dU94Z04zh4L9GTswXgMd+X/s58Csh7iXUMEUVs0Seezg
	l6RhcrlBgLwED1tZPRXFD3t/KJL1ET3YfVJnc4Io6vBX5Cxeos6CAR//VNy2YhVx
	O64j0HmO99H7v915qQ5U8/jdoRtCyMghwZ7AF3/40g8TM1weW7YEWE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=+vlmhujj7dCmfuyzOSP9EKLE1VU=; b=TgVKuE4Dg0ydDg1CZI/bKAYecw0E
	RoRlgW6purJSGKQHPbUsKpBi352i5OOfBHMtclaL//2EB0QSU4yDbtP1xi2EHceD
	NyDvVNRjD3ZqoP69ma8xzuY7EKai/QuEiXi7Bn1gK8W6cir265/wpXwtDy11ORhs
	RxOBTzvwV1uHtRY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,TW_CG,TW_YG autolearn=no version=3.3.1
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: U2FsdGVkX1+ZAAbtDB/DxU0NU3EtcZ+a
Date: Mon, 1 Apr 2013 01:03:02 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Hang on CTRL-C (was Re: livelock on sigfe)
Message-ID: <20130401050302.GA5699@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20130120065456 DOT GC17644 AT ednor DOT casa DOT cgf DOT cx> <khk62q$6n2$1 AT ger DOT gmane DOT org> <20130311143630 DOT GA6498 AT ednor DOT casa DOT cgf DOT cx> <khlbm8$5tg$1 AT ger DOT gmane DOT org> <20130311204554 DOT GA959 AT ednor DOT casa DOT cgf DOT cx> <20130315194101 DOT GA2095 AT ednor DOT casa DOT cgf DOT cx> <ki0isq$ts8$1 AT ger DOT gmane DOT org> <ki0jn6$5pl$1 AT ger DOT gmane DOT org> <20130316164446 DOT GA2240 AT ednor DOT casa DOT cgf DOT cx> <kjasrc$f1i$1 AT ger DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <kjasrc$f1i$1@ger.gmane.org>
User-Agent: Mutt/1.5.20 (2009-06-14)

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