Message 410370 - Python tracker

➜

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	eric.snow
Recipients	Quentin.Pradet, SethMichaelLarson, eric.snow
Date	2022-01-12.00:33:36
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
It looks like PyThreadState.async_exc is getting set to 0x01 somewhere. There isn't any code like that in https://github.com/python/cpython/commit/32a67246b0d1e08cd50fc3bfa58052cfeb515b2e. However, the struct layout of PyThreadState did change slightly in that commit. The ABI is generally not stable until the first beta (and sometimes a bit after that). Could it be that the wheel for one or more the dependencies was built against an earlier 3.11 release (with the previous PyThreadState layout)? If I move fields around in PyThreadState just right, I can no longer reproduce the problem.

It looks like PyThreadState.async_exc is getting set to 0x01 somewhere.  There isn't any code like that in https://github.com/python/cpython/commit/32a67246b0d1e08cd50fc3bfa58052cfeb515b2e.  However, the struct layout of PyThreadState did change slightly in that commit.

The ABI is generally not stable until the first beta (and sometimes a bit after that).  Could it be that the wheel for one or more the dependencies was built against an earlier 3.11 release (with the previous PyThreadState layout)?  

If I move fields around in PyThreadState just right, I can no longer reproduce the problem.

History
Date	User	Action	Args
2022-01-12 00:33:36	eric.snow	set	recipients: + eric.snow, Quentin.Pradet, SethMichaelLarson
2022-01-12 00:33:36	eric.snow	set	messageid: <[email protected]>
2022-01-12 00:33:36	eric.snow	link	issue46320 messages
2022-01-12 00:33:36	eric.snow	create