You can always follow the error message and try to reproduce error inside gdb. This way, you can nail the very source of the problem. If you have JVM's crash log, core file, this would also help you investigate the source of the problem.
Take a look here:
JNI debugging – extreme way, or what your iPad mini and ssh sessions can do for you
What you want to do is to start you code in debug mode, run gdb, attach to JVM and set breakpoint as described in error message.
Then, once breakpoint is hit, you can take a look at backtrace inside JVM and see where the issue happens in Java code. To me, it seems as JVM installation related issue or native code problem.
You can also take a look here, to see how to debug mixed Java/C code (in your case you will debug whole JVM) using IntelliJ:
recipeNoD002 - Debugging JNI code with IntelliJ/CLion