[pypy-dev] Emulate pypy SIGSEGV

[Pavlo Lavrenenko]

Hello, guys.

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 0x7f0d4c26ce7d in ?? () from /lib64/libpypy-c.so


If I had a proper code sample to reproduce the issue I would have submitted it 
but since I am literally chasing ghosts I am more interested in how to make PyPy 
throw SIGSEGV on purpose (the software hangs after one of its child processes 
dies with signal 11, I want to at least reproduce and workaround this).


kill -11 doesn't give the result I want. Any way to make PyPy crash somewhere in 
/lib64/libpypy-c.so?


--
Best regards,
Pavlo Lavrenenko,
PortaOne, Inc., Junior Software Developer
Tel: +1-866-SIP VOIP (+1 866 747 8647) ext. 7624

PortaOne - VoIP Solutions Company
Visit our Website: http://www.portaone.com
___
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev

Re: [pypy-dev] Emulate pypy SIGSEGV

[Armin Rigo]

Hi Pavlo,

On 3 July 2017 at 16:25, Pavlo Lavrenenko  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 0x7f0d4c26ce7d 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