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

evdev: If there was an error initializing a controller, don't proceed #1395

Merged
merged 1 commit into from Sep 20, 2018

Conversation

Projects
None yet
2 participants
@baka0815
Collaborator

baka0815 commented Sep 20, 2018

If the controller was not correctly initialized, the fd and/or the mapping might not be set, which could then result in access violations or other errors.

This fixes #1380.

evdev: If there was an error initializing a controller, don't proceed
If the controller was not correctly initialized, the fd and/or the mapping might not be set, which could then result in access violations or other errors.

@baka0815 baka0815 merged commit 4000b88 into master Sep 20, 2018

9 checks passed

LGTM analysis: C/C++ No alert changes
Details
LGTM analysis: JavaScript No alert changes
Details
LGTM analysis: Python No alert changes
Details
continuous-integration/appveyor/branch AppVeyor build succeeded
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
license/cla Contributor License Agreement is signed.
Details
wercker/build Wercker pipeline passed
Details

@baka0815 baka0815 deleted the baka/evdev_crash2 branch Sep 20, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment