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 with an evil custom mro()
on a metaclass
#92112
Labels
type-crash
A hard crash of the interpreter, possibly with a core dump
Comments
I'll open a PR shortly. |
Opened #92113. @JulienPalard |
JelleZijlstra
pushed a commit
that referenced
this issue
May 6, 2022
JelleZijlstra
pushed a commit
to JelleZijlstra/cpython
that referenced
this issue
May 6, 2022
…ythonGH-92113). (cherry picked from commit 85354ed) Co-authored-by: Alexey Izbyshev <izbyshev@ispras.ru>
JelleZijlstra
pushed a commit
to JelleZijlstra/cpython
that referenced
this issue
May 6, 2022
…ythonGH-92113). (cherry picked from commit 85354ed) Co-authored-by: Alexey Izbyshev <izbyshev@ispras.ru>
JelleZijlstra
added a commit
that referenced
this issue
May 7, 2022
hello-adam
pushed a commit
to hello-adam/cpython
that referenced
this issue
Jun 2, 2022
…ythonGH-92113) (pythonGH-92372) (cherry picked from commit 85354ed) Co-authored-by: Alexey Izbyshev <izbyshev@ispras.ru>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Crash report
There is a path in
type_mro_modified
that results in double-free of*mro_meth
:cpython/Objects/typeobject.c
Line 362 in ad5e852
cpython/Objects/typeobject.c
Line 371 in ad5e852
A reproducer:
Crash with the debug CPython:
This bug was introduced in #73052.
The text was updated successfully, but these errors were encountered: