Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

3.12: segmentation fault from compile() builtin #99708

Closed
Assignees
iritkatriel
Labels
3.12only security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)type-crashA hard crash of the interpreter, possibly with a core dump
@davidhewitt

Description

@davidhewitt

Crash report

I can trigger a crash of the 3.12 interpreter using the following Python instruction:

compile("assert (False if 1 else True)","<string>","exec")

Error messages

The full output when running locally-built cpython with debug assertions avoids a segfault, triggering an assertion instead:

$ ./pythonPython3.12.0a2+ (heads/main:f1a4a6a587,Nov222022,22:12:33) [GCC9.4.0]onlinuxType"help","copyright","credits"or"license"formoreinformation.>>>compile("assert (False if 1 else True)","<string>","exec")python:Python/compile.c:8703:remove_redundant_jumps:Assertion `no_empty_basic_blocks(g)'failed.Aborted

Your environment

I originally encountered the segmentation fault on macOS with 3.12.0a1.

I have reproduced it above withf1a4a6a on ubuntu (inside WSL).

Linked PRs

Metadata

Metadata

Assignees

Labels

3.12only security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)type-crashA hard crash of the interpreter, possibly with a core dump

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions


    [8]ページ先頭

    ©2009-2025 Movatter.jp