New submission from Alex Gaynor <alex.gay...@gmail.com>: 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...@bitbucket.org/pypy/pypy Next, get to the correct revision: hg up -C 82e1fc9c253c Finally, attempt to run the tests: ./pytest.py pypy/module/micronumpy/ -x At this point you should have a segfault that appears to be because of a bad address for a weakref (but I could be horrifically wrong). ---------- components: Interpreter Core messages: 148855 nosy: alex priority: normal severity: normal status: open title: Segfault inside of gc/weakref versions: Python 2.6, Python 2.7 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13529> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
