From: Jim Bell <Jim@JC-Bell.com>
To: cygwin@cygwin.com
Subject: Re: python fails asyncio tests (py 3.7 & 3.8)
Date: Sat, 21 Nov 2020 18:13:14 -0600 [thread overview]
Message-ID: <5233b4bb-8e9e-b6bd-0a56-c6ce5aa43f42@JC-Bell.com> (raw)
In-Reply-To: <b7b31de6-1752-a705-a169-2ef1447fd93f@JC-Bell.com>
On 2020-11-21 5:59 AM, Jim Bell wrote:
> The standard python asyncio tests hang.
>
> cd /usr/lib/python3.8/test
>
> python3.8 test_asyncore.py -v
>
> [...]
Using strace, stripping down this very repeatable test, and grabbing the
source-code snapshot, it looks like winsup/cygwin/select.cc
socket_cleanup() is waiting forever for the thread to go away.
strace:
121 6732185 [main] python3.8 13329 select_stuff::cleanup: calling
cleanup rout
ines
178 6732363 [main] python3.8 13329 socket_cleanup: si 0x800290E10
si->thread 0
x18023E758
-
But I don't see the select_printf("returning") at select.cc:1808, so
the si->thread->detach() call seems to be blocked forever. I don't see
that we make it here either:
select.cc:1685 select_printf ("leaving thread_socket");
I see a bool stop_thread field in select_info, inherited by
select_socket_info (select.h), used by other mechanisms. Seems that
could be set by socket_cleanup() and used by thread_socket() to break
out of its event loops (select.cc lines 1660 and 1667)
https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/select.cc;hb=HEAD#l1796
next prev parent reply other threads:[~2020-11-22 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 11:59 Jim Bell
2020-11-22 0:13 ` Jim Bell [this message]
2020-12-01 0:53 ` Mark Geisert
2020-12-07 7:58 ` Mark Geisert
2020-12-07 18:01 ` Marco Atzeri
2020-12-08 3:14 ` Mark Geisert
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=5233b4bb-8e9e-b6bd-0a56-c6ce5aa43f42@JC-Bell.com \
--to=jim@jc-bell.com \
--cc=cygwin@cygwin.com \
/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).