[issue46159] Segfault when using trace functions in 3.11a3

[Cyril Jouve]

Cyril Jouve  added the comment:

this looks related to https://github.com/nedbat/coveragepy/issues/1294 / 
https://github.com/nedbat/coveragepy/issues/1316 related to binary 
incompatibility in coverage (6.2) binary wheel built with 3.11alpha2 and 
running on 3.11alpha3 or later.

Latest release of coverage (6.3) do not ship binary wheel for python 3.11 
anymore, so it's installed and built with your current python.

--
nosy: +Cyril Jouve

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46159] Segfault when using trace functions in 3.11a3

[Alex Gaynor]

Alex Gaynor  added the comment:

It seems to no longer be crashing with alpha5. Hopefully it's actually fixed 
and not merely having a more subtle failure mode.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46159] Segfault when using trace functions in 3.11a3

[Mark Shannon]

Mark Shannon  added the comment:

Can you reproduce this failure with just Python?
If not, with just cryptography and not tox?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46159] Segfault when using trace functions in 3.11a3

[Quentin Pradet]

Quentin Pradet  added the comment:

Thanks, you're right, I ran `git bisect` on Linux and the commit that causes 
the issue is 
https://github.com/python/cpython/commit/135cabd328504e1648d17242b42b675cdbd0193b
 ("Copy free variables in bytecode to allow calls to inner functions to be 
specialized") from https://bugs.python.org/issue44525

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46159] Segfault when using trace functions in 3.11a3

[Paul Kehrer]

Paul Kehrer  added the comment:

Changes in ABI don't seem to be the likely culprit since the Dockerfile 
provided can demonstrate this bug and has no caching that would result in 
obtaining alpha2-based binaries.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46159] Segfault when using trace functions in 3.11a3

[Quentin Pradet]

Quentin Pradet  added the comment:

The ABI between alpha 2 and alpha 3 changed, see 
https://bugs.python.org/issue46320. If pip built (say) cffi in CI for alpha2 
and put it in the cache, then it reused that wheel for alpha3 and the segfault 
is expected.

--
nosy: +Quentin.Pradet

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46159] Segfault when using trace functions in 3.11a3

[Alex Gaynor]

Change by Alex Gaynor :


--
components: +Interpreter Core
nosy: +Mark.Shannon, alex

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46159] Segfault when using trace functions in 3.11a3

[Paul Kehrer]

Change by Paul Kehrer :


--
title: Segfault -> Segfault when using trace functions in 3.11a3

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com