This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Hang on CTRL-C (was Re: livelock on sigfe)
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