strange sigsegv with gdb

| 分类 Develop  | 标签 jni 

is this true?

according to: http://stackoverflow.com/questions/13132669/strange-sigsegv-while-calling-java-code-from-c-through-jni

This was indeed what technomage had suggested in the comments. The gdb crash was a red herring because of jvm throwing SIGSEGV which was meant to be handled by jvm.

Once I tell gdb "handle SIGSEGV nostop", it works just fine and I was able to debug my larger program.


上一篇     下一篇