Serafeim Mellos added the comment:
Ok, I understand your point about PyObject_New not initializing custom fields
(although it looks like something is initializing the memory since it's not
random, it's either 0x0 or 0x1).
However, if that's the expected behavior, it'
Serafeim Mellos added the comment:
Actually, I'm not so sure it's related to memory management after all judging
by this (but I don't really know how the compilation part is supposed to work
:)):
(gdb) watch *0x77ec0680
Hardware watchpoint 1: *0x77ec0680
(gdb) b
Serafeim Mellos added the comment:
Backtrace from segfault is below but I'm not very familiar with python's memory
internals in order to figure out where is the value initialized at the first
place
(gdb) bt
#0 _Py_XDECREF (op=0x1) at
/home/fim/.pyenv/versions/3.8-dev/include/
New submission from Serafeim Mellos :
I looked but I couldn't find any mention of this either in the bug tracker or
the docs so I assume this is not a desired behavior or a known proble but feel
free to correct me if I'm wrong.
I have noticed a weird behavior in Python3.7 onward
