[issue29884] faulthandler does not properly restore sigaltstack during teardown

2017-03-24 Thread Christophe Zeitouny
Changes by Christophe Zeitouny <ch...@tich.info>: -- pull_requests: +704 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29884> ___

[issue29884] faulthandler does not properly restore sigaltstack during teardown

2017-03-24 Thread Christophe Zeitouny
Changes by Christophe Zeitouny <ch...@tich.info>: -- pull_requests: +703 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29884> ___

[issue29884] faulthandler does not properly restore sigaltstack during teardown

2017-03-22 Thread Christophe Zeitouny
Changes by Christophe Zeitouny <ch...@tich.info>: -- pull_requests: +682 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29884> ___

[issue29884] faulthandler does not properly restore sigaltstack during teardown

2017-03-22 Thread Christophe Zeitouny
Changes by Christophe Zeitouny <ch...@tich.info>: Added file: http://bugs.python.org/file46755/python_reproducer.cpp ___ Python tracker <rep...@bugs.python.org> <http://bugs.python

[issue29884] faulthandler does not properly restore sigaltstack during teardown

2017-03-22 Thread Christophe Zeitouny
New submission from Christophe Zeitouny: Looks like faulthandler is not properly tearing down its sigaltstack, causing potential double-free issues in any application that embeds the Python interpreter. I stumbled upon this when I enabled AddressSanitizer on my application, which sets up