GCC issue still here?

Jean-Pierre Flori jpflori@gmail.com
Fri Jan 16 22:44:00 GMT 2015

Dear all,

I once again stumbled on issues reminding me of the ones mentioned here:
and here on the cygwin ml:

Looking at the tickets on GCC tracker:
and at the merged fix:
the fix looks slightly different, it does not deregister using the
suggested condition...

Would you say there still is a problem or should I look further into this?

Here is the backtrace I get with latest Cygwin GCC 4.9.2 when Python
exits and unregisters a lot of modules:

(gdb) bt
#0  0x0028db58 in ?? ()
#1  0x75ca12cc in WriteFile () from /cygdrive/c/Windows/syswow64/kernel32.dll
#2  0x610df5bd in sig_send(_pinfo*, siginfo_t&, _cygtls*) ()
   from /usr/bin/cygwin1.dll
#3  0x610dcbac in _pinfo::kill(siginfo_t&) () from /usr/bin/cygwin1.dll
#4  0x610dd076 in kill0(int, siginfo_t&) () from /usr/bin/cygwin1.dll
#5  0x610dd242 in raise () from /usr/bin/cygwin1.dll
#6  0x610dd4e3 in abort () from /usr/bin/cygwin1.dll
#7  0x6fa742e1 in cyggcc_s-1!.deregister_frame_info_bases ()
   from /usr/bin/cyggcc_s-1.dll
#8  0x5a6f1112 in __gcc_deregister_frame ()
   from C:/cygwin/home/jp/sage.git/local/lib/python2.7/lib-dynload/time.dll
#9  0x61164681 in __call_exitprocs () from /usr/bin/cygwin1.dll
#10 0x6113b1b8 in exit () from /usr/bin/cygwin1.dll
#11 0x61006d49 in cygwin_exit () from /usr/bin/cygwin1.dll
#12 0x610082e6 in cygwin_exit_return () from /usr/bin/cygwin1.dll
#13 0x61006044 in _cygtls::call2(unsigned long (*)(void*, void*), void*, void*)
    () from /usr/bin/cygwin1.dll
#14 0x610061b6 in _cygtls::call(unsigned long (*)(void*, void*), void*) ()
   from /usr/bin/cygwin1.dll
#15 0x61007164 in _dll_crt0@0 () from /usr/bin/cygwin1.dll
#16 0x00401202 in cygwin_crt0 (f=0x401740 <main>)
    at /usr/src/debug/cygwin-1.7.33-1/winsup/cygwin/lib/cygwin_crt0.c:22
#17 0x00401015 in mainCRTStartup ()
    at /usr/src/debug/cygwin-1.7.33-1/winsup/cygwin/crt0.c:29


Jean-Pierre Flori

More information about the Cygwin-apps mailing list