Android Fatal signal 11 (SIGSEGV) at 0x636f7d89 (code=1). How can it be tracked down?

Question

I\'ve been reading the other posts on tracking down the reasons for getting a SIGSEGV in an Android app. I plan to scour my app for possible NullPointers relate

Answer 1

If you had added some native C code in your project this answer could be helpful.

I had added some native C code in android project.

Now i was trying to access that code which was returning native string to me, before processing the the string i had set its default value as nullptr. Now upon retrieving its value in java code ran into this issue.

As our native C code is out from java directory so getting no clue of exact line of code which is creating the issue. So i would suggest you to check your .cpp file and try to find any clue there.

Hope so you will get rid of the issue soon. :)