[PyPy-issue] [issue524] intermittent seg fault
pypy-dev-issue at codespeak.net
Tue Apr 27 18:13:05 CEST 2010
Fijal <fijall at gmail.com> added the comment:
I can't reproduce the segfault (surprise, surprise), do you have original thing
that caused segfault with no parts removed? Also there is a couple of ways of
getting gdb traceback. First is to get core file "ulimit -c 100000000" should
do. Then you can do gdb pypy-c core and look there.
You might want a debug build of pypy - you grab sources from
/tmp/usession-trunk-<num or username>/testing_1 and run make debug (or make
lldebug) there. This will create a ./testing_1 executable which is pypy-c.
Feel free to drop by on #pypy on irc.freenode.net so we can look at the issue.
Thanks for feedback.
status: unread -> chatting
PyPy development tracker <pypy-dev-issue at codespeak.net>
More information about the Pypy-issue