Clicking Quest controller trigger causes Android Studio debugger to break on a SIGILL

Development Platform & Builds Mobile
, , ,
1

Attempting to debug an engine crash, I did a Debug Editor build of UE4.26.2.

I packaged a Debug build for Android ASTC (Android build settings configured to target Oculus Mobile (Quest)).

Followed these instructions to attach the Android Studio debugger. (also had to do Build → Clean Project in Android Studio as discussed here ).

Whenever I click the trigger button on the Quest’s controller, the VR rendering on the Quest freezes and Android Studio breaks on a SIGILL signal… this was confusing me and preventing me from testing with the debugger attached until I found out what was going on / how to make it not break.

2

This is actually documented by Oculus here https://developer.oculus.com/documentation/native/android/mobile-studio-debug/ , although it’s easy to miss if you’re just looking at Unreal-related documentation.

As Oculus explains, to prevent Quest controller key presses from breaking into the debugger, in Android Studio, go to “Run → Edit Configurations”. Click the “Debugger” tab, then “LLDB Post Attach Commands”. Click the + button and add the command process handle --pass true --stop false --notify true SIGILL