[issue38006] _PyFunction_Vectorcall() can segfault on process exit

STINNER Victor added the comment: Using gdb, I checked if func_clear() can be cleared outside func_dealloc(): yes, delete_garbage() (gcmodule.c) calls type->clear(). But I'm surprised that the function would be seen as "unreachable" if it's reference counter was equal to 135: (gdb) print fu

[issue38006] _PyFunction_Vectorcall() can segfault on process exit

Change by Karthikeyan Singaravelan : -- nosy: +jdemeyer ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue38006] _PyFunction_Vectorcall() can segfault on process exit

STINNER Victor added the comment: > I don't understand how the function ended up with func_code=NULL. That > shouldn't be a valid function to call, IMO. Do you have any info on how the > function ended up in that state? It doesn't seem possible to create a function with func_code=NULL, nor t

[issue38006] _PyFunction_Vectorcall() can segfault on process exit

Christian Heimes added the comment: Not yet. My current hypothesis is the function code object is already cleaned up *somehow*. -- ___ Python tracker ___ ___

[issue38006] _PyFunction_Vectorcall() can segfault on process exit

Petr Viktorin added the comment: I don't understand how the function ended up with func_code=NULL. That shouldn't be a valid function to call, IMO. Do you have any info on how the function ended up in that state? -- ___ Python tracker

[issue38006] _PyFunction_Vectorcall() can segfault on process exit

New submission from Christian Heimes : I have a case of a segfault on Fedora 32 (currently rawhide) with Python 3.8b4 and FreeIPA. The ipactl Python helper crashes with a segfault when the Python process exits. The segfault occurs in _PyFunction_Vectorcall() with a weakref related local scope