public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: jojelino <jojelino@gmail.com>
To: cygwin@cygwin.com
Subject: Re: deadlock with busy waiting on sigfe
Date: Mon, 11 Mar 2013 08:54:00 -0000	[thread overview]
Message-ID: <khk62q$6n2$1@ger.gmane.org> (raw)
In-Reply-To: <20130120065456.GC17644@ednor.casa.cgf.cx>

On 2013-01-20 PM 3:54, Christopher Faylor wrote:
> On Sun, Jan 20, 2013 at 02:23:23PM +0900, jojelino wrote:
> Once again: don't care about your backtraces.  Submit a proper bug report.
>
> cgf
>
And found another livelock with CYGWIN_NT-5.2 F8G6S6D42HGDY4 
1.7.18s(0.263/5/3) 20130309 21:57:01 i686 Cygwin provided in 
http://cygwin.org/snapshots/cygwin1-20130309.dll.bz2
I can't submit proper bug report. it just hangs during CTRL+C for 
arbitrary cygwin executable and there is nothing i can do except dumping 
backtrace. If you don't care about it, it's ok to ignore this. please 
pass by.
Thread 2 (Thread 7596.0x104):
#0  0x7c96845c in ntdll!KiFastSystemCallRet ()
    from /cygdrive/c/WINDOWS/system32/ntdll.dll
#1  0x7c9678c9 in ntdll!ZwSetInformationThread ()
    from /cygdrive/c/WINDOWS/system32/ntdll.dll
#2  0x7c8324f9 in SetThreadPriority ()
    from /cygdrive/c/WINDOWS/system32/kernel32.dll
#3  0x6108790d in yield ()
     at 
/netrel/src/cygwin-snapshot-20130309-1/winsup/cygwin/miscfuncs.cc:253
#4  0x610d7354 in _cygtls::lock() () from /usr/bin/cygwin1.dll
#5  0x6103096e in sigpacket::setup_handler (this=0x6aac34,
     handler=0x6102fe00 <signal_exit(int, siginfo_t*)>, siga=..., 
tls=0x22ce64)
     at 
/netrel/src/cygwin-snapshot-20130309-1/winsup/cygwin/exceptions.cc:796
#6  0x610318ff in sigpacket::process (this=0x6aac34)
     at 
/netrel/src/cygwin-snapshot-20130309-1/winsup/cygwin/exceptions.cc:1245
---Type <return> to continue, or q <return> to quit---
#7  0x610dd74c in wait_sig ()
     at /netrel/src/cygwin-snapshot-20130309-1/winsup/cygwin/sigproc.cc:1389
#8  0x61003ea5 in cygthread::callfunc (this=0x6118b420 <threads>,
     issimplestub=<optimized out>)
     at /netrel/src/cygwin-snapshot-20130309-1/winsup/cygwin/cygthread.cc:51
#9  0x6100442f in cygthread::stub (arg=0x6118b420 <threads>)
     at /netrel/src/cygwin-snapshot-20130309-1/winsup/cygwin/cygthread.cc:93
#10 0x6100537d in _cygtls::call2 (this=<optimized out>,
     func=0x610043e0 <cygthread::stub(void*)>, arg=0x6118b420 <threads>,
     buf=0x6100551b <_cygtls::call(unsigned long (*)(void*, void*), 
void*)+91>)
     at /netrel/src/cygwin-snapshot-20130309-1/winsup/cygwin/cygtls.cc:99
#11 0x006affb8 in ?? ()
#12 0x7c82484f in KERNEL32!GetModuleHandleA ()
    from /cygdrive/c/WINDOWS/system32/kernel32.dll
#13 0x00000000 in ?? ()

Thread 1 (Thread 7596.0x190):
#0  0x7c96845c in ntdll!KiFastSystemCallRet ()
    from /cygdrive/c/WINDOWS/system32/ntdll.dll
#1  0x7c9678c9 in ntdll!ZwSetInformationThread ()
    from /cygdrive/c/WINDOWS/system32/ntdll.dll
#2  0x7c8324f9 in SetThreadPriority ()
    from /cygdrive/c/WINDOWS/system32/kernel32.dll
#3  0x610878cb in yield ()
---Type <return> to continue, or q <return> to quit---
     at 
/netrel/src/cygwin-snapshot-20130309-1/winsup/cygwin/miscfuncs.cc:244
#4  0x610d7354 in _cygtls::lock() () from /usr/bin/cygwin1.dll
#5  0x61031297 in _cygtls::call_signal_handler (
     this=0x610d7354 <_cygtls::lock()+23>)
     at 
/netrel/src/cygwin-snapshot-20130309-1/winsup/cygwin/exceptions.cc:1265
#6  0x61007689 in _cygwin_exit_return ()
     at /netrel/src/cygwin-snapshot-20130309-1/winsup/cygwin/dcrt0.cc:1012
#7  0x6100537d in _cygtls::call2 (this=<optimized out>,
     func=0x61006c50 <dll_crt0_1(void*)>, arg=0x0,
     buf=0x6100551b <_cygtls::call(unsigned long (*)(void*, void*), 
void*)+91>)
     at /netrel/src/cygwin-snapshot-20130309-1/winsup/cygwin/cygtls.cc:99
#8  0x0022ff78 in ?? ()
#9  0x004011d2 in ?? ()
#10 0x00401015 in ?? ()
#11 0x7c82f243 in ProcessIdToSessionId ()
    from /cygdrive/c/WINDOWS/system32/kernel32.dll

-- 
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

  reply	other threads:[~2013-03-11  8:54 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 [this message]
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='khk62q$6n2$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).