Skip to content

[3.6] bpo-26558: Fix Py_FatalError() with GIL released (GH-10267) #10270

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
Merged
merged 1 commit into from
Nov 1, 2018
Merged

[3.6] bpo-26558: Fix Py_FatalError() with GIL released (GH-10267) #10270

merged 1 commit into from
Nov 1, 2018

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented Oct 31, 2018 •
edited by bedevere-bot
Loading

Don't call _Py_FatalError_PrintExc() nor flush_std_files() if the
current thread doesn't hold the GIL, or if the current thread
has no Python state thread.

(cherry picked from commit 3a228ab)

https://bugs.python.org/issue26558

@vstinner
bpo-26558: Fix Py_FatalError() with GIL released (GH-10267)
feddc67 
Don't call _Py_FatalError_PrintExc() nor flush_std_files() if the
current thread doesn't hold the GIL, or if the current thread
has no Python state thread.

(cherry picked from commit 3a228ab)
@bedevere-bot bedevere-bot mentioned this pull request Oct 31, 2018
Merged
@vstinner vstinner merged commit ff56597 into python:3.6 Nov 1, 2018
@vstinner vstinner deleted the fatal_error36 branch November 1, 2018 00:11
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
skip news
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@vstinner @the-knights-who-say-ni @bedevere-bot