[issue13992] Segfault in PyTrash_destroy_chain
Charles-François Natali
report at bugs.python.org
Sun Feb 12 16:47:30 CET 2012
Charles-François Natali <neologix at free.fr> added the comment:
> Possibly a double free?
> (gdb) p *op
> $5 = {_ob_next = 0x0, _ob_prev = 0x0, ob_refcnt = 0, ob_type = 0x3c6d9f0}
>
It indeed looks like a double free (see the previous and next pointers
have already been set to NULL).
Could you check if there's not another thread active inside the
interpreter at the same time ("thread apply all bt")?
But I'm afraid it'll be hard to debug with just a core dump.
Do you have any test script that could be used to reproduce the crash?
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13992>
_______________________________________
More information about the Python-bugs-list
mailing list