You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running example/core/core_input_gamepad example program crashes with a EXC_BAD_ACCESS (SIGSEGV) when one disconnects the USB cable. This is mostly due to minimal error checking in the core_input_gamepad example code. Disconnecting the gamepad is a reasonable thing to do, and there is an opportunity in raylib to avoid this scenario (see PR #2121 that I've put a fix in).
Environment
Macbook Pro, macOS Big Sur Version 11.6 Intel, OpenGL ES 3.0 Renderer: Intel(R) Iris(TM) Plus Graphics 650
Issue description
Running example/core/core_input_gamepad example program crashes with a EXC_BAD_ACCESS (SIGSEGV) when one disconnects the USB cable. This is mostly due to minimal error checking in the core_input_gamepad example code. Disconnecting the gamepad is a reasonable thing to do, and there is an opportunity in raylib to avoid this scenario (see PR #2121 that I've put a fix in).
Environment
Macbook Pro, macOS Big Sur Version 11.6 Intel, OpenGL ES 3.0 Renderer: Intel(R) Iris(TM) Plus Graphics 650
Issue Screenshot
sigsegv.pdf
Code Example
I've raised a PR #2121 with a fix.
The text was updated successfully, but these errors were encountered: