As described in this issue, Java VM take it as normal to signal SIGSEGV null reference access in Java code during startup, which is converted to a NullPointerException and then caught and handled by Java code to adjust and continue. Yet, it still imposes troubles while debugging JNI native code. The following command help suppress and ignore such signals:
- Clang LLDB:
process handle SIGSEGV --notify true --pass true --stop false- GDB
handle SIGSEGV nostop