Hi Frank, You would need to compile pypy with “--lldebug”, then run your workload in GDB to see where it crashes. Another option is to obtain a core dump (if you cannot run the workload directly in GDB), then analyze the core dump in GDB. Please see [1] and [2] for this.
[1] http://stackoverflow.com/questions/6152232/how-to-generate-core-dump-file-in-ubuntu [2] http://stackoverflow.com/questions/8305866/how-to-analyze-a-programs-core-dump-file-with-gdb Regards, Florin From: pypy-dev [mailto:pypy-dev-bounces+florin.papa=intel....@python.org] On Behalf Of Frank Wang Sent: Tuesday, April 4, 2017 8:31 AM To: PyPy Developer Mailing List <pypy-dev@python.org> Subject: [pypy-dev] Debugging SegFaults Hi, I made some modifications to pypy, but the new pypy-c binary results in a segfault on certain instructions. What's the easiest way to do a traceback to see what led to the segfault? Thanks, Frank
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
