Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
05e92213
Commit
05e92213
authored
Feb 02, 2019
by
native-api
Committed by
Steve Dower
Feb 02, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
bpo-33316: PyThread_release_lock always fails (GH-6541)
Use correct interpretation of return value from APIs.
parent
00e9c55d
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
4 additions
and
2 deletions
+4
-2
Misc/NEWS.d/next/Windows/2018-04-20-03-24-07.bpo-33316.9IiJ8J.rst
...S.d/next/Windows/2018-04-20-03-24-07.bpo-33316.9IiJ8J.rst
+1
-0
Python/thread_nt.h
Python/thread_nt.h
+3
-2
No files found.
Misc/NEWS.d/next/Windows/2018-04-20-03-24-07.bpo-33316.9IiJ8J.rst
0 → 100644
View file @
05e92213
PyThread_release_lock always fails
Python/thread_nt.h
View file @
05e92213
...
...
@@ -104,8 +104,9 @@ LeaveNonRecursiveMutex(PNRMUTEX mutex)
if
(
PyMUTEX_LOCK
(
&
mutex
->
cs
))
return
FALSE
;
mutex
->
locked
=
0
;
result
=
PyCOND_SIGNAL
(
&
mutex
->
cv
);
result
&=
PyMUTEX_UNLOCK
(
&
mutex
->
cs
);
/* condvar APIs return 0 on success. We need to return TRUE on success. */
result
=
!
PyCOND_SIGNAL
(
&
mutex
->
cv
);
PyMUTEX_UNLOCK
(
&
mutex
->
cs
);
return
result
;
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment