8000 Segfault on ``cls.__dict__['__new__'].__annotations__`` · Issue #125017 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

Segfault on cls.__dict__['__new__'].__annotations__ #125017

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.

Sign up for GitHub

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

Jump to bottom
Closed
AA-Turner opened this issue Oct 6, 2024 · 2 comments
Closed

Segfault on cls.__dict__['__new__'].__annotations__ #125017

AA-Turner opened this issue Oct 6, 2024 · 2 comments
Assignees
@JelleZijlstra
Labels
3.14 bugs and security fixes interpreter-core (Objects, Python, Grammar, and Parser dirs) type-crash A hard crash of the interpreter, possibly with a core dump

Comments

@AA-Turner
Copy link
Member
AA-Turner commented Oct 6, 2024 •
edited by bedevere-app bot
Loading

Crash report

What happened?

The following is a reproducer of (another) segfault discovered when trying to test Python 3.14 in CI for Sphinx:

class Spam:
    def __new__(cls, x, y):
        pass


if __name__ == '__main__':
    assert Spam.__new__.__annotations__ == {}
    obj = Spam.__dict__['__new__']
    assert isinstance(obj, staticmethod)
    getattr(obj, '__annotations__', None)  # segfault here
    try:
        obj.__annotations__  # and here (absent the above)
    except AttributeError:
        pass
    print('no segfault!')

Whilst checking __annotations__ directly is somewhat convoluted, it was originally triggered by inspect.isasyncgenfunction(), which calls inspect._signature_is_functionlike() via _has_code_flag().

A similar error occurs with __class_getitem__ and __init_subclass__, but not with user-defined methdods declared with either classmethod or staticmethod. As the reproducer demonstrates, the segfault only happens with the descriptor object from __dict__ -- cls.__new__.__annotations__ is fine.

Bisection showed this to be due to d28afd3 (#119864), cc @JelleZijlstra

d28afd3fa064db10a2eb2a65bba33e8ea77a8fcf is the first bad commit
commit d28afd3fa064db10a2eb2a65bba33e8ea77a8fcf
Author: Jelle Zijlstra <jelle.zijlstra@gmail.com>
Date:   Fri May 31 14:05:51 2024 -0700

    gh-119180: Lazily wrap annotations on classmethod and staticmethod (#119864)

A

CPython versions tested on:

CPython main branch

Operating systems tested on:

Linux

Output from running 'python -VV' on the command line:

Python 3.14.0a0 (bisect/bad:d28afd3fa06, Oct 6 2024, 01:35:23) [GCC 13.2.0]

Linked PRs
@AA-Turner AA-Turner added interpreter-core (Objects, Python, Grammar, and Parser dirs) type-crash A hard crash of the interpreter, possibly with a core dump 3.14 bugs and security fixes labels Oct 6, 2024
This was referenced Oct 6, 2024
Merged
8000
Merged
@JelleZijlstra JelleZijlstra self-assigned this Oct 6, 2024
@ZeroIntensity
Copy link
Member

@JelleZijlstra I took a quick glance at the implementation and PR, and I think this is a matter of forgetting to initialize sm_dict and cm_dict in constructors. IIRC, if tp_dictoffset is used, the dictionary won't get created until someone tries to access __dict__, so here it ends up being NULL, and thus segfaulting.

@JelleZijlstra
Copy link
Member

Thanks @ZeroIntensity, I agree that's the right diagnosis. Found a related crash too:

Python 3.14.0a1+ (heads/main-dirty:a5a7f5e16d8, Oct 16 2024, 22:38:43) [Clang 15.0.0 (clang-1500.3.9.4)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> @classmethod
... def f(): pass
... 
>>> del f.__annotations__
Assertion failed: (!_PyErr_Occurred(tstate)), function _PyEval_EvalFrameDefault, file generated_cases.c.h, line 5059.
Abort trap: 6

JelleZijlstra added a commit to JelleZijlstra/cpython that referenced this issue Oct 17, 2024
@JelleZijlstra
pythongh-125017: Fix crash on premature access to classmethod/staticm…
3b22aed 
…ethod annotations
@bedevere-app bedevere-app bot mentioned this issue Oct 17, 2024
Merged
JelleZijlstra added a commit that referenced this issue Oct 17, 2024
@JelleZijlstra
gh-125017: Fix crash on premature access to classmethod/staticmethod …
f203d1c 
…annotations (#125636)
zware added a commit to zware/cpython that referenced this issue Oct 17, 2024
@zware
pythongh-125017: Fix refleak from pythonGH-125636
6d876da
@bedevere-app bedevere-app bot mentioned this issue Oct 17, 2024
Merged
zware added a commit that referenced this issue Oct 17, 2024
@zware
gh-125017: Fix refleak from GH-125636 (GH-125664)
c3164ae
@AA-Turner AA-Turner mentioned this issue Oct 19, 2024
Merged
ebonnal pushed a commit to ebonnal/cpython that referenced this issue Jan 12, 2025
@JelleZijlstra @ebonnal
pythongh-125017: Fix crash on premature access to classmethod/staticm…
82803b2 
…ethod annotations (python#125636)
ebonnal pushed a commit to ebonnal/cpython that referenced this issue Jan 12, 2025
@zware @ebonnal
pythongh-125017: Fix refleak from pythonGH-125636 (pythonGH-125664)
cae280d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JelleZijlstra JelleZijlstra

Labels
3.14 bugs and security fixes interpreter-core (Objects, Python, Grammar, and Parser dirs) type-crash A hard crash of the interpreter, possibly with a core dump
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@JelleZijlstra @AA-Turner @ZeroIntensity
0