public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Maarten Jacobs <maarten256@hotmail.com>
To: "Martens, Robert EY28737" <robert.martens@bell.ca>,
	"cygwin@cygwin.com"	<cygwin@cygwin.com>
Subject: RE: Python stackdump on "succesful" exit after import of python-requests
Date: Sun, 31 Jan 2016 13:37:00 -0000	[thread overview]
Message-ID: <BLU170-W99FA16FE5288347E01FB999EDC0@phx.gbl> (raw)
In-Reply-To: <7dd1bf85a74041df90f65fb31e9279fe@DG4MBX01-WYN.bell.corp.bce.ca>

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

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 installed 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/pythonrun.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/Windows/SysWOW64/ntdll.dll
#2 0x765014b9 in WaitForSingleObjectEx () from /cygdrive/c/Windows/syswow64/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

  reply	other threads:[~2016-01-30 23:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-30 15:21 Martens, Robert (EY28737)
2016-01-31 13:37 ` Maarten Jacobs [this message]
2016-02-01  4:55   ` Maarten Jacobs
2016-02-01  5:36     ` Maarten Jacobs
2016-02-02  2:05       ` Maarten Jacobs
2016-02-02  5:58         ` Martens, Robert (EY28737)
2016-02-02 16:34           ` Maarten Jacobs
2016-02-04  4:32             ` Maarten Jacobs

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=BLU170-W99FA16FE5288347E01FB999EDC0@phx.gbl \
    --to=maarten256@hotmail.com \
    --cc=cygwin@cygwin.com \
    --cc=robert.martens@bell.ca \
    /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).