[issue29884] faulthandler does not properly restore sigaltstack during teardown

Mariatta Wijaya added the comment: PR was merged and backported into 3.5 and 3.6, so I'm closing this. Thanks, Christophe :) -- nosy: +Mariatta resolution: -> fixed stage: -> resolved status: open -> closed versions: +Python 3.5, Python 3.6, Python 3.7

[issue29884] faulthandler does not properly restore sigaltstack during teardown

Changes by Christophe Zeitouny : -- pull_requests: +704 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue29884] faulthandler does not properly restore sigaltstack during teardown

Changes by Christophe Zeitouny : -- pull_requests: +703 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue29884] faulthandler does not properly restore sigaltstack during teardown

Changes by Christophe Zeitouny : -- pull_requests: +682 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue29884] faulthandler does not properly restore sigaltstack during teardown

Changes by Christophe Zeitouny : Added file: http://bugs.python.org/file46755/python_reproducer.cpp ___ Python tracker ___ ___ Python-bugs-lis

[issue29884] faulthandler does not properly restore sigaltstack during teardown

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 and t