-
-
Notifications
You must be signed in to change notification settings - Fork 31.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash in _PyXI_ApplyErrorCode() #126986
Labels
3.13
bugs and security fixes
3.14
new features, bugs and security fixes
interpreter-core
(Objects, Python, Grammar, and Parser dirs)
topic-subinterpreters
type-crash
A hard crash of the interpreter, possibly with a core dump
Comments
ericsnowcurrently
added a commit
that referenced
this issue
Nov 19, 2024
We replace it with _PyErr_SetInterpreterAlreadyRunning().
Affecting 3.13(t) as well:
|
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Nov 19, 2024
…h-126988) We replace it with _PyErr_SetInterpreterAlreadyRunning(). (cherry picked from commit d6b3e78) Co-authored-by: Eric Snow <[email protected]>
ericsnowcurrently
added a commit
to ericsnowcurrently/cpython
that referenced
this issue
Nov 21, 2024
…h-126988) We replace it with _PyErr_SetInterpreterAlreadyRunning().
ericsnowcurrently
added a commit
that referenced
this issue
Nov 21, 2024
…h-127112) This is a pseudo-backport of d6b3e78 (gh-126988). In that change for 3.14+, we dropped _PyInterpreterState_FailIfNotRunning() and added _PyErr_SetInterpreterAlreadyRunning(). Here, we replace usage of _PyInterpreterState_FailIfNotRunning() with the inlined equivalent of _PyErr_SetInterpreterAlreadyRunning(), without adding that function. That way we avoid changing the 3.13 ABI.
ebonnal
pushed a commit
to ebonnal/cpython
that referenced
this issue
Jan 12, 2025
…h-126988) We replace it with _PyErr_SetInterpreterAlreadyRunning().
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
3.13
bugs and security fixes
3.14
new features, bugs and security fixes
interpreter-core
(Objects, Python, Grammar, and Parser dirs)
topic-subinterpreters
type-crash
A hard crash of the interpreter, possibly with a core dump
Crash report
Bug description:
This is a problem in Python/crossinterp.c, as exposed by the _interpreters module.
reproducer:
_PyXI_Enter()
, which emits the_PyXI_ERR_ALREADY_RUNNING
error code_PyXI_ApplyError()
_PyXI_ApplyError()
calls_PyInterpreterState_FailIfNotRunning()
to raise the exception, but it doesn't raise anythingI noticed this while working on gh-126914.
CPython versions tested on:
3.14
Operating systems tested on:
No response
Linked PRs
The text was updated successfully, but these errors were encountered: