From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 52869 invoked by alias); 4 Feb 2016 04:32:15 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 52604 invoked by uid 89); 4 Feb 2016 04:32:15 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KAM_ASCII_DIVIDERS,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=cygwin32, explaining, sk:unwind, sk:unwind- X-HELO: BLU004-OMC1S6.hotmail.com Received: from blu004-omc1s6.hotmail.com (HELO BLU004-OMC1S6.hotmail.com) (65.55.116.17) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA256 encrypted) ESMTPS; Thu, 04 Feb 2016 04:32:11 +0000 Received: from BLU170-W97 ([65.55.116.9]) by BLU004-OMC1S6.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Wed, 3 Feb 2016 20:32:09 -0800 X-TMN: [HlPIpZsBsy4uIWobAAmOkX8p4khD6g1s] Message-ID: From: Maarten Jacobs To: "Martens, Robert EY28737" CC: "cygwin@cygwin.com" Subject: RE: Python stackdump on "succesful" exit after import of python-requests Date: Thu, 04 Feb 2016 04:32:00 -0000 In-Reply-To: References: <7dd1bf85a74041df90f65fb31e9279fe@DG4MBX01-WYN.bell.corp.bce.ca>,,,,,<109e1012-ea7f-4852-b548-2116de770061@email.android.com>, Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes X-SW-Source: 2016-02/txt/msg00032.txt.bz2 Hi Robert, Well, your suggestion definitely helped. I did a reinstall of my 32-bit Cyg= win, and the problem with Python persisted. Then, I spent time setting up m= y 64-bit Cygwin, and the problem went away!! So - it would appear to me that running the 32-bit Cygwin Python on a 64-bi= t OS doesn't work properly. Right now I don't have a good way to verify whe= ther the problem persists with a 32-bit Cygwin on a 32-bit OS. In any event - I crossed this hurdle, and while I am now even further from = explaining what causes this issue, I appear to have a more satisfactory wor= k-around. On to the next set of issues for me. Please let me know if you can confirm the same results? (i.e. Cygwin32/OS64= doesn't work but Cygwin64/OS64 does) Thanks, Maarten ---------------------------------------- > From: maarten256@hotmail.com > To: robert.martens@bell.ca > CC: cygwin@cygwin.com > Subject: RE: Python stackdump on "succesful" exit after import of python-= requests > Date: Tue, 2 Feb 2016 11:34:49 -0500 > > Hi Robert, > > My experience with Python is very, very limited. The only reason I am loo= king into this issue is because one of the packages I want to install won't= work because of this :) > > Therefore, if you could send me a sample Python script that causes the pr= oblem on your end, I'd be more than happy to try it out on my end and see i= f it causes the same issue... Without me having to learn how to write Pytho= n. > > Your comment about a "fresh" install is intriguing and I will definitely = try that out for myself. As an aside, I am running into this issue on a 32-= bit install, is that where you found the problem initially? > > Thanks, > > Maarten > > ---------------------------------------- >> From: robert.martens@bell.ca >> To: maarten256@hotmail.com >> CC: cygwin@cygwin.com >> Subject: RE: Python stackdump on "succesful" exit after import of python= -requests >> Date: Tue, 2 Feb 2016 05:58:11 +0000 >> >> Hello Maarten, >> I won't be a lot of help with the low level debugging here but I do have= some suggestions. >> The issue occurs for me whenever I import 'requests', could you try impo= rting that module in your tests see if it also happens to you? >> >> I'm wondering if this is just a common problem between modules or if it = is inherit in python itself. >> >> The other thing I noticed is that in a fresh install of 64 bit cygwin, t= he issue does not occur! >> >> I'm going to see if I can isolate it further... >> >> Thanks for your help! >> -- >> Robert Martens >> 613 807 6137 >> ADMS System Administrator >> >> On Feb 1, 2016 9:05 PM, Maarten Jacobs wrote: >> Still whittling away at this issue. I installed a few more debug librari= es, and the traceback now looks like: >> >> (gdb) r generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml >> Starting program: /usr/bin/python generator.py libvirt /usr/share/libvir= t/api/libvirt-api.xml >> [New Thread 6688.0x730] >> [New Thread 6688.0x1d44] >> [New Thread 6688.0x1c68] >> [New Thread 6688.0x12d8] >> Found 406 functions in /usr/share/libvirt/api/libvirt-api.xml >> Found 0 functions in libvirt-override-api.xml >> Generated 338 wrapper functions >> Done! >> >> Program received signal SIGABRT, Aborted. >> 0x66b73de4 in Py_Exit () at /usr/src/debug/python-2.7.10-1/Python/python= run.c:1780 >> 1780 exit(sts); >> (gdb) bt >> #0 0x66b73de4 in Py_Exit () at /usr/src/debug/python-2.7.10-1/Python/pyt= honrun.c:1780 >> #1 0x76e8e091 in WaitForSingleObjectEx () from /cygdrive/c/WINDOWS/SYSTE= M32/KERNELBASE.dll >> #2 0x76e8dff2 in WaitForSingleObject () from /cygdrive/c/WINDOWS/SYSTEM3= 2/KERNELBASE.dll >> #3 0x610f2730 in sig_send(_pinfo*, siginfo_t&, _cygtls*)@12 (p=3Dp@entry= =3D0x60fd0000, si=3D..., tls=3Dtls@entry=3D0x0) >> at /usr/src/debug/cygwin-2.4.1-1/winsup/cygwin/sigproc.cc:716 >> #4 0x610ef4cc in _pinfo::kill(siginfo_t&)@8 (this=3D0x60fd0000, si=3D...= ) at /usr/src/debug/cygwin-2.4.1-1/winsup/cygwin/signal.cc:252 >> #5 0x610ef9d8 in kill0 (pid=3Dpid@entry=3D6688, si=3D...) at /usr/src/de= bug/cygwin-2.4.1-1/winsup/cygwin/signal.cc:303 >> #6 0x610efbb2 in kill (sig=3Dsig@entry=3D6, pid=3D6688) at /usr/src/debu= g/cygwin-2.4.1-1/winsup/cygwin/signal.cc:312 >> #7 raise (sig=3Dsig@entry=3D6) at /usr/src/debug/cygwin-2.4.1-1/winsup/c= ygwin/signal.cc:288 >> #8 0x610efe79 in abort () at /usr/src/debug/cygwin-2.4.1-1/winsup/cygwin= /signal.cc:375 >> #9 0x6deb43c1 in __deregister_frame_info_bases (begin=3D0x6e200000 <__EH= _FRAME_BEGIN__>) at /usr/src/debug/gcc-4.9.3-1/libgcc/unwind-dw2-fde.c:216 >> #10 0x6e1e10e2 in __gcc_deregister_frame () from /usr/bin/cygexpat-1.dll >> #11 0x61028bb7 in per_module::run_dtors (this=3D0x6130d658) at /usr/src/= debug/cygwin-2.4.1-1/winsup/cygwin/dll_init.cc:81 >> #12 dll::run_dtors (this=3D0x6130d650) at /usr/src/debug/cygwin-2.4.1-1/= winsup/cygwin/dll_init.h:72 >> #13 dll_global_dtors () at /usr/src/debug/cygwin-2.4.1-1/winsup/cygwin/d= ll_init.cc:53 >> #14 0x6118d64d in __call_exitprocs (code=3Dcode@entry=3D0, d=3Dd@entry= =3D0x0) at /usr/src/debug/cygwin-2.4.1-1/newlib/libc/stdlib/__call_atexit.c= :118 >> #15 0x6114ae88 in exit (code=3D0) at /usr/src/debug/cygwin-2.4.1-1/newli= b/libc/stdlib/exit.c:66 >> #16 0x61006e79 in cygwin_exit (n=3D0) at /usr/src/debug/cygwin-2.4.1-1/w= insup/cygwin/dcrt0.cc:1337 >> #17 0x610ebf85 in _sigfe () at sigfe.s:38 >> #18 0x66b73de4 in Py_Exit (sts=3Dsts@entry=3D0) at /usr/src/debug/python= -2.7.10-1/Python/pythonrun.c:1780 >> #19 0x66ba5281 in handle_system_exit () at /usr/src/debug/python-2.7.10-= 1/Python/pythonrun.c:1152 >> #20 0x66b7413e in handle_system_exit () at /usr/src/debug/python-2.7.10-= 1/Python/pythonrun.c:1193 >> #21 PyErr_PrintEx (set_sys_last_vars=3Dset_sys_last_vars@entry=3D1) at /= usr/src/debug/python-2.7.10-1/Python/pythonrun.c:1162 >> #22 0x66b74bc7 in PyErr_Print () at /usr/src/debug/python-2.7.10-1/Pytho= n/pythonrun.c:1065 >> #23 PyRun_SimpleFileExFlags (fp=3D, filename=3D0x60cc5c "= generator.py", closeit=3D1, flags=3D0x60cb5c) >> at /usr/src/debug/python-2.7.10-1/Python/pythonrun.c:953 >> #24 0x66b8ae9e in Py_Main (argc=3Dargc@entry=3D4, argv=3Dargv@entry=3D0x= 60cc1c) at /usr/src/debug/python-2.7.10-1/Modules/main.c:640 >> #25 0x00401750 in main (argc=3D4, argv=3D0x60cc1c) at /usr/src/debug/pyt= hon-2.7.10-1/Modules/python.c:23 >> >> Having pored over this traceback 100 times now, the current questions I'= m trying to figure out, and I'd like some help with: >> >> 1. #20 of the traceback shows "0x66b7413e in handle_system_exit () at /u= sr/src/debug/python-2.7.10-1/Python/pythonrun.c:1193" doesn't make sense si= nce line 1193 of pythonrun.c is not anywhere near "handle_system_exit()". L= ine 1152 on #19 IS in handle_system_exit(). Does this mean the traceback is= no good? >> >> 2. #10 of the traceback shows "#10 0x6e1e10e2 in __gcc_deregister_frame = () from /usr/bin/cygexpat-1.dll" - I cannot for the life of me figure out h= ow I get debug symbols for this? >> >> Thanks, >> >> Maarten Jacobs >> >> ---------------------------------------- >>> From: maarten256@hotmail.com >>> To: cygwin@cygwin.com >>> CC: robert.martens@bell.ca >>> Subject: RE: Python stackdump on "succesful" exit after import of pytho= n-requests >>> Date: Mon, 1 Feb 2016 00:36:02 -0500 >>> >>> I installed the debug version of gcc and the traceback became a little = more readable: >>> >>> (gdb) bt >>> #0 0x66b73de4 in Py_Exit () at /usr/src/debug/python-2.7.10-1/Python/py= thonrun.c:1780 >>> #1 0x76e8e091 in WaitForSingleObjectEx () from /cygdrive/c/WINDOWS/SYST= EM32/KERNELBASE.dll >>> #2 0x76e8dff2 in WaitForSingleObject () from /cygdrive/c/WINDOWS/SYSTEM= 32/KERNELBASE.dll >>> #3 0x610f2730 in sig_send(_pinfo*, siginfo_t&, _cygtls*)@12 (p=3Dp@entr= y=3D0x60fd0000, si=3D..., tls=3Dtls@entry=3D0x0) at /usr/src/debug/cygwin-2= .4.1-1/winsup/cygwin/sigproc.cc:716 >>> #4 0x610ef4cc in _pinfo::kill(siginfo_t&)@8 (this=3D0x60fd0000, si=3D..= .) at /usr/src/debug/cygwin-2.4.1-1/winsup/cygwin/signal.cc:252 >>> #5 0x610ef9d8 in kill0 (pid=3Dpid@entry=3D4080, si=3D...) at /usr/src/d= ebug/cygwin-2.4.1-1/winsup/cygwin/signal.cc:303 >>> #6 0x610efbb2 in kill (sig=3Dsig@entry=3D6, pid=3D4080) at /usr/src/deb= ug/cygwin-2.4.1-1/winsup/cygwin/signal.cc:312 >>> #7 raise (sig=3Dsig@entry=3D6) at /usr/src/debug/cygwin-2.4.1-1/winsup/= cygwin/signal.cc:288 >>> #8 0x610efe79 in abort () at /usr/src/debug/cygwin-2.4.1-1/winsup/cygwi= n/signal.cc:375 >>> #9 0x6deb43c1 in __deregister_frame_info_bases (begin=3D0x6e200000) at = /usr/src/debug/gcc-4.9.3-1/libgcc/unwind-dw2-fde.c:216 >>> #10 0x6e1e10e2 in ?? () from /usr/bin/cygexpat-1.dll >>> #11 0x61028bb7 in per_module::run_dtors (this=3D0x6130d6c0) at /usr/src= /debug/cygwin-2.4.1-1/winsup/cygwin/dll_init.cc:81 >>> #12 dll::run_dtors (this=3D0x6130d6b8) at /usr/src/debug/cygwin-2.4.1-1= /winsup/cygwin/dll_init.h:72 >>> #13 dll_global_dtors () at /usr/src/debug/cygwin-2.4.1-1/winsup/cygwin/= dll_init.cc:53 >>> #14 0x6118d64d in __call_exitprocs (code=3Dcode@entry=3D0, d=3Dd@entry= =3D0x0) at /usr/src/debug/cygwin-2.4.1-1/newlib/libc/stdlib/__call_atexit.c= :118 >>> #15 0x6114ae88 in exit (code=3D0) at /usr/src/debug/cygwin-2.4.1-1/newl= ib/libc/stdlib/exit.c:66 >>> #16 0x61006e79 in cygwin_exit (n=3D0) at /usr/src/debug/cygwin-2.4.1-1/= winsup/cygwin/dcrt0.cc:1337 >>> #17 0x610ebf85 in _sigfe () at sigfe.s:38 >>> #18 0x66b73de4 in Py_Exit (sts=3Dsts@entry=3D0) at /usr/src/debug/pytho= n-2.7.10-1/Python/pythonrun.c:1780 >>> #19 0x66ba5281 in handle_system_exit () at /usr/src/debug/python-2.7.10= -1/Python/pythonrun.c:1152 >>> #20 0x66b7413e in handle_system_exit () at /usr/src/debug/python-2.7.10= -1/Python/pythonrun.c:1193 >>> #21 PyErr_PrintEx (set_sys_last_vars=3Dset_sys_last_vars@entry=3D1) at = /usr/src/debug/python-2.7.10-1/Python/pythonrun.c:1162 >>> #22 0x66b74bc7 in PyErr_Print () at /usr/src/debug/python-2.7.10-1/Pyth= on/pythonrun.c:1065 >>> #23 PyRun_SimpleFileExFlags (fp=3D, filename=3D0x60cc5c = "generator.py", closeit=3D1, flags=3D0x60cb5c) at /usr/src/debug/python-2.7= .10-1/Python/pythonrun.c:953 >>> #24 0x66b8ae9e in Py_Main (argc=3Dargc@entry=3D4, argv=3Dargv@entry=3D0= x60cc1c) at /usr/src/debug/python-2.7.10-1/Modules/main.c:640 >>> #25 0x00401750 in main (argc=3D4, argv=3D0x60cc1c) at /usr/src/debug/py= thon-2.7.10-1/Modules/python.c:23 >>> (gdb) up 9 >>> #9 0x6deb43c1 in __deregister_frame_info_bases (begin=3D0x6e200000) at = /usr/src/debug/gcc-4.9.3-1/libgcc/unwind-dw2-fde.c:216 >>> 216 gcc_assert (ob); >>> (gdb) >>> >>> So looks like the problem occurs on an "assert". I need to dig further = into this - but that's for tomorrow / later this week. >>> >>> Thanks, >>> >>> Maarten Jacobs >>> >>> ---------------------------------------- >>>> From: maarten256@hotmail.com >>>> To: cygwin@cygwin.com >>>> CC: robert.martens@bell.ca >>>> Subject: RE: Python stackdump on "succesful" exit after import of pyth= on-requests >>>> Date: Sun, 31 Jan 2016 23:55:14 -0500 >>>> >>>> I realized that for me, the "work-around" to use python3 was not pract= ical, so I am back to analyzing this problem... And not making much progres= s. Some help/assistance would be appreciated! >>>> >>>> I got the following traceback: >>>> >>>> (gdb) r generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml >>>> Starting program: /usr/bin/python generator.py libvirt /usr/share/libv= irt/api/libvirt-api.xml >>>> [New Thread 7028.0xb4] >>>> [New Thread 7028.0x1998] >>>> [New Thread 7028.0x1070] >>>> [New Thread 7028.0x15d8] >>>> [New Thread 7028.0x1d38] >>>> >>>> Found 406 functions in /usr/share/libvirt/api/libvirt-api.xml >>>> Found 0 functions in libvirt-override-api.xml >>>> Generated 338 wrapper functions >>>> >>>> Program received signal SIGABRT, Aborted. >>>> 0x66b73de4 in Py_Exit () at /usr/src/debug/python-2.7.10-1/Python/pyth= onrun.c:1780 >>>> 1780 exit(sts); >>>> (gdb) bt >>>> #0 0x66b73de4 in Py_Exit () at /usr/src/debug/python-2.7.10-1/Python/p= ythonrun.c:1780 >>>> #1 0x76e8e091 in WaitForSingleObjectEx () from /cygdrive/c/WINDOWS/SYS= TEM32/KERNELBASE.dll >>>> #2 0x76e8dff2 in WaitForSingleObject () from /cygdrive/c/WINDOWS/SYSTE= M32/KERNELBASE.dll >>>> #3 0x610f2730 in sig_send(_pinfo*, siginfo_t&, _cygtls*)@12 (p=3Dp@ent= ry=3D0x60fd0000, si=3D..., tls=3Dtls@entry=3D0x0) at /usr/src/debug/cygwin-= 2.4.1-1/winsup/cygwin/sigproc.cc:716 >>>> #4 0x610ef4cc in _pinfo::kill(siginfo_t&)@8 (this=3D0x60fd0000, si=3D.= ..) at /usr/src/debug/cygwin-2.4.1-1/winsup/cygwin/signal.cc:252 >>>> #5 0x610ef9d8 in kill0 (pid=3Dpid@entry=3D7028, si=3D...) at /usr/src/= debug/cygwin-2.4.1-1/winsup/cygwin/signal.cc:303 >>>> #6 0x610efbb2 in kill (sig=3Dsig@entry=3D6, pid=3D7028) at /usr/src/de= bug/cygwin-2.4.1-1/winsup/cygwin/signal.cc:312 >>>> #7 raise (sig=3Dsig@entry=3D6) at /usr/src/debug/cygwin-2.4.1-1/winsup= /cygwin/signal.cc:288 >>>> #8 0x610efe79 in abort () at /usr/src/debug/cygwin-2.4.1-1/winsup/cygw= in/signal.cc:375 >>>> #9 0x6deb43c1 in cyggcc_s-1!.deregister_frame_info_bases () from /usr/= bin/cyggcc_s-1.dll >>>> #10 0x6e1e10e2 in ?? () from /usr/bin/cygexpat-1.dll >>>> #11 0x61028bb7 in per_module::run_dtors (this=3D0x6130d980) at /usr/sr= c/debug/cygwin-2.4.1-1/winsup/cygwin/dll_init.cc:81 >>>> #12 dll::run_dtors (this=3D0x6130d978) at /usr/src/debug/cygwin-2.4.1-= 1/winsup/cygwin/dll_init.h:72 >>>> #13 dll_global_dtors () at /usr/src/debug/cygwin-2.4.1-1/winsup/cygwin= /dll_init.cc:53 >>>> #14 0x6118d64d in __call_exitprocs (code=3Dcode@entry=3D0, d=3Dd@entry= =3D0x0) at /usr/src/debug/cygwin-2.4.1-1/newlib/libc/stdlib/__call_atexit.c= :118 >>>> #15 0x6114ae88 in exit (code=3D0) at /usr/src/debug/cygwin-2.4.1-1/new= lib/libc/stdlib/exit.c:66 >>>> #16 0x61006e79 in cygwin_exit (n=3D0) at /usr/src/debug/cygwin-2.4.1-1= /winsup/cygwin/dcrt0.cc:1337 >>>> #17 0x610ebf85 in _sigfe () at sigfe.s:38 >>>> #18 0x66b73de4 in Py_Exit (sts=3Dsts@entry=3D0) at /usr/src/debug/pyth= on-2.7.10-1/Python/pythonrun.c:1780 >>>> #19 0x66ba5281 in handle_system_exit () at /usr/src/debug/python-2.7.1= 0-1/Python/pythonrun.c:1152 >>>> #20 0x66b7413e in handle_system_exit () at /usr/src/debug/python-2.7.1= 0-1/Python/pythonrun.c:1193 >>>> #21 PyErr_PrintEx (set_sys_last_vars=3Dset_sys_last_vars@entry=3D1) at= /usr/src/debug/python-2.7.10-1/Python/pythonrun.c:1162 >>>> #22 0x66b74bc7 in PyErr_Print () at /usr/src/debug/python-2.7.10-1/Pyt= hon/pythonrun.c:1065 >>>> #23 PyRun_SimpleFileExFlags (fp=3D, filename=3D0x60cc5c= "generator.py", closeit=3D1, flags=3D0x60cb5c) at /usr/src/debug/python-2.= 7.10-1/Python/pythonrun.c:953 >>>> #24 0x66b8ae9e in Py_Main (argc=3Dargc@entry=3D4, argv=3Dargv@entry=3D= 0x60cc1c) at /usr/src/debug/python-2.7.10-1/Modules/main.c:640 >>>> #25 0x00401750 in main (argc=3D4, argv=3D0x60cc1c) at /usr/src/debug/p= ython-2.7.10-1/Modules/python.c:23 >>>> >>>> I'm used to looking at tracebacks from C++ executables, so most of thi= s feels familiar. >>>> >>>> It would appear that deregister_frame_info_bases () (on #9) causes the= abort to happen. As far as I have been able to figure out, all of this hap= pens while the instance of Python is being shut down. >>>> >>>> This is also not a new problem, as this was apparently already reporte= d in November of 2014: >>>> >>>> http://readlist.com/lists/cygwin.com/cygwin/15/75280.html >>>> >>>> Unfortunately that thread does not go any further than what is also ap= parent from my traceback. >>>> >>>> Does anybody have suggestions on how to further debug this issue? >>>> >>>> Thanks, >>>> >>>> Maarten Jacobs >>>> >>>>> From: maarten256@hotmail.com >>>>> To: robert.martens@bell.ca; cygwin@cygwin.com >>>>> Subject: RE: Python stackdump on "succesful" exit after import of pyt= hon-requests >>>>> Date: Sat, 30 Jan 2016 18:21:45 -0500 >>>>> >>>>> Interesting - I had the same issue earlier this week; I worked around= it by using python3 instead, which didn't cause the same issue. (I figured= it was just me not doing something right). >>>>> >>>>> Obviously that doesn't explain the behavior but I didn't have time to= further investigate the issue with python 2.7. >>>>> >>>>> I ran into the issue when I was trying to build libvirt-python on Cyg= win. >>>>> >>>>> I'd be curious to know what the real root cause for this abort is. >>>>> >>>>> Thanks, >>>>> >>>>> Maarten Jacobs >>>>> >>>>> ---------------------------------------- >>>>> From: robert.martens@bell.ca >>>>> To: cygwin@cygwin.com >>>>> Subject: Python stackdump on "succesful" exit after import of python-= requests >>>>> Date: Fri, 29 Jan 2016 21:38:54 +0000 >>>>> >>>>> >>>>> Hello, >>>>> I am having a strange issue with Python 2.7 on cygwin. >>>>> Whenever a script of mine imports 'requests' (python-requests install= ed via cygwin installer), after it closes I get an "Aborted" message and a = stack dump. >>>>> >>>>> This consistently causes the issue: >>>>> $ python >>>>> Python 2.7.10 (default, Jun 1 2015, 18:17:45) >>>>> [GCC 4.9.2] on cygwin >>>>> Type "help", "copyright", "credits" or "license" for more information. >>>>>>>> import requests >>>>>>>> exit() >>>>> Aborted (core dumped) >>>>> >>>>> And here is the stackdump >>>>> $ cat python2.7.exe.stackdump >>>>> Stack trace: >>>>> Frame Function Args >>>>> 0028C868 61033A23 (00000244, 0000EA60, 000000A4, 0028C8D8) >>>>> 0028C998 610F27E2 (000000C8, 000000CC, 000000B8, 6111295F) >>>>> >>>>> This is what gdb says: >>>>> (gdb) r >>>>> Starting program: /usr/bin/python >>>>> [New Thread 8744.0x1ca0] >>>>> [New Thread 8744.0x24f4] >>>>> [New Thread 8744.0x192c] >>>>> [New Thread 8744.0x11f0] >>>>> Python 2.7.10 (default, Jun 1 2015, 18:17:45) >>>>> [GCC 4.9.2] on cygwin >>>>> Type "help", "copyright", "credits" or "license" for more information. >>>>>>>> import requests >>>>> [New Thread 8744.0x2380] >>>>>>>> quit() >>>>> >>>>> Program received signal SIGABRT, Aborted. >>>>> 0x65c63de4 in Py_Exit () at /usr/src/debug/python-2.7.10-1/Python/pyt= honrun.c:1780 >>>>> 1780 exit(sts); >>>>> (gdb) bt >>>>> #0 0x65c63de4 in Py_Exit () at /usr/src/debug/python-2.7.10-1/Python/= pythonrun.c:1780 >>>>> #1 0x770ff8d1 in ntdll!ZwWaitForSingleObject () from /cygdrive/c/Wind= ows/SysWOW64/ntdll.dll >>>>> #2 0x765014b9 in WaitForSingleObjectEx () from /cygdrive/c/Windows/sy= swow64/KERNELBASE.dll >>>>> #3 0x000002f8 in ?? () >>>>> #4 0x00000000 in ?? () >>>>> (gdb) continue >>>>> Continuing. >>>>> [New Thread 8744.0x25c4] >>>>> 3 [main] python2.7 8744 cygwin_exception::open_stackdumpfile: Dumping= stack trace to python2.7.exe.stackdump >>>>> [Thread 8744.0x24f4 exited with code 34304] >>>>> [Thread 8744.0x25c4 exited with code 34304] >>>>> [Thread 8744.0x2380 exited with code 34304] >>>>> [Thread 8744.0x192c exited with code 34304] >>>>> [Inferior 1 (process 8744) exited with code 0103000] >>>>> >>>>> Any ideas? >>>>> >>>>> Thanks, >>>>> Robert Martens >>>>> ADMS >>>>> >>>>> >>>>> -- >>>>> 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 >>>>> >>>>> -- >>>>> 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 >>>>> >>>> >>>> -- >>>> 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 >>>> >>> >>> -- >>> 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 >>> >> >> >> -- >> 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 >> > > -- > 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 > =20=09=09=20=09=20=20=20=09=09=20=20 -- 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