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
multiprocessing: Possible uninitialized pointer use in Windows builds #71778
Comments
Originally reported (if you can call it "reported") here: http://www.viva64.com/en/b/0414/ AFAICT, this is an easy and inconsequential fix. |
LGTM |
Berker, I don't push code to CPython (I have the commitbit for PEP editing), so do you want to push that? |
Yes, that's why I assigned it to myself :) Thanks for the patch! |
Cool cool! Then someone will need to notify the PVS-Studio people that we've fixed the two bugs that are actually our bugs :) |
It's a little strange that nobody reports a multiprocessing crash on Windows before. It looks like ResetEvent() is called with a random number (coming from the uninitialized stack memory). Windows is probably smart and does nothing if the argument is not a known handle of an event object. |
I suggested a different way to fix the issue on the review. Python 2.7 is not affected by the bug, but Python 3.5 and 3.6 are affected. |
Here is an updated patch. Thanks, Victor. |
issue27591_v2.diff LGTM except of a minor comment (PEP-7!) on the review. |
New changeset da955567d7c7 by Berker Peksag in branch '3.5': New changeset d5f796da4013 by Berker Peksag in branch 'default': |
Thanks! I should read PEP-7 again :) |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: