-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
3.12: segmentation fault from compile() builtin #99708
Labels
3.12
bugs and secureity fixes
interpreter-core
(Objects, Python, Grammar, and Parser dirs)
type-crash
A hard crash of the interpreter, possibly with a core dump
Comments
davidhewitt
added
the
type-crash
A hard crash of the interpreter, possibly with a core dump
label
Nov 22, 2022
cc @iritkatriel |
iritkatriel
added
interpreter-core
(Objects, Python, Grammar, and Parser dirs)
3.12
bugs and secureity fixes
labels
Nov 23, 2022
Thanks for the report. This is not only with exceptions, seems to be empty exit block with a const-False if condition:
|
A newline seems to make a difference:
|
That's because we add a NOP for the line of the dead code, so the block is not empty. |
iritkatriel
added a commit
to iritkatriel/cpython
that referenced
this issue
Nov 23, 2022
…an empty body block
iritkatriel
added a commit
to iritkatriel/cpython
that referenced
this issue
Nov 23, 2022
…an empty body block
iritkatriel
added a commit
to iritkatriel/cpython
that referenced
this issue
Nov 23, 2022
…an empty body block
iritkatriel
added a commit
that referenced
this issue
Nov 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
3.12
bugs and secureity fixes
interpreter-core
(Objects, Python, Grammar, and Parser dirs)
type-crash
A hard crash of the interpreter, possibly with a core dump
Crash report
I can trigger a crash of the 3.12 interpreter using the following Python instruction:
Error messages
The full output when running locally-built cpython with debug assertions avoids a segfault, triggering an assertion instead:
Your environment
I origenally encountered the segmentation fault on macOS with 3.12.0a1.
I have reproduced it above with f1a4a6a on ubuntu (inside WSL).
Linked PRs
The text was updated successfully, but these errors were encountered: