Skip to content

bpo-35823: subprocess: Fix handling of pthread_sigmask() errors #22944

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 24, 2020

Conversation

izbyshev
Copy link
Contributor

@izbyshev izbyshev commented Oct 24, 2020

Using POSIX_CALL() is incorrect since pthread_sigmask() returns
the error number instead of setting errno.

Also handle failure of the first call to pthread_sigmask()
in the parent process, and explain why we don't handle failure
of the second call.

https://bugs.python.org/issue35823

Using POSIX_CALL() is incorrect since pthread_sigmask() returns
the error number instead of setting errno.

Also handle failure of the first call to pthread_sigmask()
in the parent process, and explain why we don't handle failure
of the second call.
@izbyshev izbyshev requested a review from gpshead as a code owner October 24, 2020 17:13
@gpshead gpshead added skip news type-bug An unexpected behavior, bug, or error labels Oct 24, 2020
Copy link
Member

@gpshead gpshead left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch, pthread_sigmask is unusual for posix in this sense. thanks!

@gpshead gpshead merged commit 473db47 into python:master Oct 24, 2020
@izbyshev izbyshev deleted the bpo-35823-pthread-sigmask-fixup branch October 24, 2020 17:48
adorilson pushed a commit to adorilson/cpython that referenced this pull request Mar 13, 2021
…onGH-22944)

Using POSIX_CALL() is incorrect since pthread_sigmask() returns
the error number instead of setting errno.

Also handle failure of the first call to pthread_sigmask()
in the parent process, and explain why we don't handle failure
of the second call in a comment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip news type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants