-
-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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
Segfault in invalid concurrent.futures.interpreter.WorkerContext
#127165
Comments
I'm assuming this is because of a missing |
If you can, give it to me :) |
Apparently, this is because |
There is a private _PyUnicode_AsUTF8NoNUL() function which rejects null characters. |
…pythonGH-127199) (cherry picked from commit 46bfd26) Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
Crash report
What happened?
It's possible to segfault the interpreter by calling
initialize()
on aconcurrent.futures.interpreter.WorkerContext
instance that was created with theshared
argument being a dict containing the null byte as a key:This doesn't require threads or free-threading. It can be traced to the
_interpreters
module:The backtrace is:
Found using fusil by @vstinner.
CPython versions tested on:
3.14, CPython main branch
Operating systems tested on:
Linux
Output from running 'python -VV' on the command line:
Python 3.14.0a2+ (heads/main:0af4ec3, Nov 20 2024, 21:45:19) [GCC 13.2.0]
Linked PRs
_interpreters
#127199_interpreters
(GH-127199) #127463The text was updated successfully, but these errors were encountered: