The stack backtrace provides a full stack trace of the failing native thread. You can use the stack backtrace to determine if a crash is caused by an error in the JVM or the native application.
Stack backtrace for failing native thread ========================================= Native thread id: 0x000A4081 ./libj9ute24.so:0xD20BBC0C [0xD20AA000 +0x00011C0C] ./libj9ute24.so:0xD20BB634 [0xD20AA000 +0x00011634] ./libj9ute24.so:0xD20BC010 [0xD20AA000 +0x00012010] ./libj9ute24.so:0xD20BCE00 [0xD20AA000 +0x00012E00] ./libj9trc24.so:0xD1724320 [0xD171A000 +0x0000A320] ./libj9vm24.so:0xD1626078 [0xD161B000 +0x0000B078] ./libj9vm24.so:0xD161F1CC [0xD161B000 +0x000041CC] ./libj9vm24.so:0xD16294C0 [0xD161B000 +0x0000E4C0] ./libj9vm24.so:0xD16259FC [0xD161B000 +0x0000A9FC] ./libj9prt24.so:0xD20C88F0 [0xD20C5000 +0x000038F0] ./libj9vm24.so:0xD162C2A8 [0xD161B000 +0x000112A8] ./libj9vm24.so:0xD165B39C [0xD161B000 +0x0004039C] j9:0x10002950 [0x10000000 +0x00002950] j9:0x10001FA8 [0x10000000 +0x00001FA8] ./libj9prt24.so:0xD20C88F0 [0xD20C5000 +0x000038F0] j9:0x10001F3C [0x10000000 +0x00001F3C] j9:0x100001B4 [0x10000000 +0x000001B4] ------------------------------------------------------------------------The example shown is from a 32-bit JVM. The output is similar for 64-bit JVMs.