NotificationsYou must be signed in to change notification settings
Fork33.3k
Star69.7k

[3.14] gh-137185: Fix`_Py_DumpStack()` async signal safety (gh-137187)#137206

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

colesbury merged 2 commits intopython:3.14frommiss-islington:backport-11a8652-3.14

Oct 7, 2025

Merged

[3.14] gh-137185: Fix`_Py_DumpStack()` async signal safety (gh-137187)#137206

colesbury merged 2 commits intopython:3.14frommiss-islington:backport-11a8652-3.14

Oct 7, 2025

Conversation

Copy link

Contributor

miss-islington commentedJul 29, 2025•
edited by bedevere-appbot
Loading

Call backtrace() once when installing the signal handler to ensure that
libgcc is dynamically loaded outside the signal handler.

This fixes a "signal-unsafe call inside of a signal" TSan error from
test_faulthandler.test_enable_fd.
(cherry picked from commit11a8652)

Co-authored-by: Sam Grosscolesbury@gmail.com

Issue:_Py_DumpStack() is not signal-safe the first time it's called #137185

pythongh-137185: Fix_Py_DumpStack()async signal safety (pythongh-…

204a342

…137187)Call backtrace() once when installing the signal handler to ensure thatlibgcc is dynamically loaded outside the signal handler.This fixes a "signal-unsafe call inside of a signal" TSan error fromtest_faulthandler.test_enable_fd.(cherry picked from commit11a8652)Co-authored-by: Sam Gross <colesbury@gmail.com>