[issue13529] Segfault inside of gc/weakref

Alex Gaynor added the comment: Turns out this was a subtle bug in some raw memory manipulation code, which amaury spotted. -- resolution: -> invalid status: open -> closed ___ Python tracker

[issue13529] Segfault inside of gc/weakref

Alex Gaynor added the comment: Antoine asked for a gdb bt, here's the last couple of useful frames: #0 _PyWeakref_ClearRef (self=0x4000) at Objects/weakrefobject.c:97 #1 0x004d4c66 in handle_weakrefs (old=0x78a2b0, unreachable=0x7fff87b0) at Modules/gcmodule.c:595 #2

[issue13529] Segfault inside of gc/weakref

New submission from Alex Gaynor : I don't have a particularly minimal test case for this, however I am able to reproduce it consistently (so far reproduced on multiple machines, 32-bit and 64-bit on 2.6 and 2.7), using these steps: First get a checkout of the PyPy repository: hg clone ssh://h