Cygwin python coredump on import uuid, subprocess

[Crestez Dan Leonard <cdleonard at gmail dot com>]

Hello,

This issue appears in a longer script but I was able to restrict it to import order. The following script crashes:

    #! /usr/bin/env python
    import uuid
    import subprocess

    $ python coredump.py
    Aborted (core dumped)

Changing the import order makes it exit successfully:

    #! /usr/bin/env python
    import subprocess
    import uuid

Other python scrips generally work fine.

I also ran the failing test through gdb:

$ gdb --args /usr/bin/python coredump.py
GNU gdb (GDB) 7.6.50.20130728-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-pc-cygwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
..
Reading symbols from /usr/bin/python2.7.exe...Reading symbols from /usr/lib/debug/usr/bin/python2.7.exe.dbg...done.
done.
(gdb) r
Starting program: /usr/bin/python2.7.exe coredump.py
[New Thread 4156.0x1574]
[New Thread 4156.0x1540]
[New Thread 4156.0x1160]

Program received signal SIGABRT, Aborted.
0x0028da18 in ?? ()
(gdb) bt
#0  0x0028da18 in ?? ()
#1  0x76fa1194 in WaitForSingleObjectEx () from /cygdrive/c/Windows/syswow64/kernel32.dll
#2  0x76fa1148 in WaitForSingleObject () from /cygdrive/c/Windows/syswow64/kernel32.dll
#3  0x610da470 in sig_send(_pinfo*, siginfo_t&, _cygtls*)@12 (p=0x60fd0000, p@entry=0x0, si=..., tls=tls@entry=0x0) at /usr/src/debug/cygwin-1.7.28-2/winsup/cygwin/sigproc.cc:665
#4  0x610d78bc in _pinfo::kill(siginfo_t&)@8 (this=0x0, si=...) at /usr/src/debug/cygwin-1.7.28-2/winsup/cygwin/signal.cc:248
#5  0x00000011 in ?? ()
#6  0x00000004 in ?? ()
#7  0x0028a96c in ?? ()
#8  0x00003bd0 in ?? ()
#9  0x00419f88 in ?? ()
Cannot access memory at address 0x1533f549

It seems odd to me that threads are created for such a simple script.

This is python 2.7 on cygwin x86 on windows 7 64-bit (redacted cygcheck attached). It also reproduces on another cleaner Windows XP 32-bit machine.

Regards,
Leonard

Attachment: win7-cygcheck.out
Description: Text document

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