This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skrah
Recipients Phil Frost, facundobatista, mark.dickinson, rhettinger, skrah, tim.peters, vstinner
Date 2019-06-06.16:49:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559839772.27.0.686822647206.issue37168@roundup.psfhosted.org>
In-reply-to
Content
There are lots of ideas still. :)

As I said, on a Linux other than RedHat or Debian or such I'd first try
to blame the shipped Python, then the libc (I had a glibc memmove issue
once with similar inexplicable results).

Alpine Linux apparently uses musl.  Is that well supported and tested?



Since you mention concurrency: Before the arrival of contextvars in 3.7
the decimal context is thread-safe, but not coroutine-safe.


If the issue is really in that particular loop I can't see how
that could be the cause, but perhaps the core dump is not accurate.
History
Date User Action Args
2019-06-06 16:49:32skrahsetrecipients: + skrah, tim.peters, rhettinger, facundobatista, mark.dickinson, vstinner, Phil Frost
2019-06-06 16:49:32skrahsetmessageid: <1559839772.27.0.686822647206.issue37168@roundup.psfhosted.org>
2019-06-06 16:49:32skrahlinkissue37168 messages
2019-06-06 16:49:32skrahcreate