I just started seeing this problem myself --- on 1.7.22 release.

On 5/22/2013 5:31 AM, Corinna Vinschen wrote:
> On May 22 11:11, Denis Excoffier wrote:
>> Hello,
>>
>> With the current snapshot (20130521) on Windows XP, the following
>> fails (with an empty stackdump):
>>
>> % /usr/bin/python pyfoo
>> Abort (core dumped)
>> % cat pyfoo
>> import xml.sax
>> xml.sax.make_parser()
>> % cat python2.7.exe.stackdump
>> Stack trace:
>> Frame     Function  Args
>> % /usr/bin/python --version
>> Python 2.7.3
>> %
>>
>> With some dichotomy, i found that under the 20130430 snapshot it works
>> (no "abort", no stackdump), but under 20130501 it does the same
>> as today (ie abort).
> 
> I have another effect.  In my case the 20130430 snapshot does not
> print the "Abort (core dumped)" message, but it still creates the
> more or less empty stackdump file as above.  So, AFAICS, the crash
> occured before, only you didn't see it.  With Cygwin 1.7.17,
> I only get an "Abort" and an entirely empty stackdump.

I can run python -c 'import _wp,sqlite3' and see Python abort, but if I swap the
module order, everything seems to be fine. gdb is useless if I wait until it
breaks, but if i set a breakpoint on cygwin1!abort beforehand, I get this stack:

(gdb) where
#0  abort () at /usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/signal.cc:362
#1  0xc3b05111 in cyggcc_s-1!__deregister_frame_info_bases () from
/usr/bin/cyggcc_s-1.dll
#2  0x65fc10e2 in __gcc_deregister_frame () from C:/users/dancol/wptools/_wp.dll
#3  0x610265f5 in run_dtors (this=<optimized out>)
    at /usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/dll_init.cc:80
#4  run_dtors (this=<optimized out>) at
/usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/dll_init.h:72
#5  run_dtors (this=<optimized out>) at
/usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/dll_init.cc:41
#6  dll_global_dtors () at
/usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/dll_init.cc:52

Does that help at all?  I only started seeing this problem after I recompiled
_wp.dll using gcc 4.7.3.