Hi Pavlo, On 3 July 2017 at 16:25, Pavlo Lavrenenko <sa...@portaone.com> wrote: > Running PyPy 5.6.0 with GCC 4.8.5 20150623 (Red Hat 4.8.5-4) here. > Occasionally PyPy terminates with signal 11 and a long stack consisting > mostly of: #31 0x00007f0d4c26ce7d in ?? () from /lib64/libpypy-c.so
I would try first upgrading to PyPy 5.8.0. > kill -11 doesn't give the result I want. Any way to make PyPy crash > somewhere in /lib64/libpypy-c.so? ``os.kill(os.getpid(), signal.SIGSEGV)``? If that's what you tried and it doesn't give the results you want, please explain in more details why not. A bientôt, Armin. _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
