Skip to content

gh-96652: Check previous signal handler to be non-NULL #96660

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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 3 commits into from
Closed

gh-96652: Check previous signal handler to be non-NULL #96660

wants to merge 3 commits into from

Conversation

ovchinnikov-v-a
Copy link

@ovchinnikov-v-a ovchinnikov-v-a commented Sep 7, 2022 •
edited by bedevere-bot
Loading

For systems without sigaction (i.e. HAVE_SIGACTION is undefined) faulthandler_user has to check previous signal handler to be defined (non-NULL) before calling it. Otherwise the code is subject to segmentation faults.

pythongh-96652: Check previous signal handler to be non-NULL
f397724 
For systems without `sigaction` (i.e. HAVE_SIGACTION is undefined)
`faulthandler_user` has to check previous signal handler to be
defined (non-NULL) before calling it. Otherwise the code is
subject to segmentation faults.
@bedevere-bot
Copy link

Most changes to Python require a NEWS entry.

Please add it using the blurb_it web app or the blurb command-line tool.

@ghost
Copy link

ghost commented Sep 7, 2022 •
edited by ghost
Loading

All commit authors signed the Contributor License Agreement.
CLA signed

@sobolevn sobolevn mentioned this pull request Sep 8, 2022
Merged
@ovchinnikov-v-a
Copy link
Author

#96666 supersedes this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
awaiting review
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ovchinnikov-v-a @bedevere-bot