My android application crashes in the native layer with no message whatsoever

Question

My android application crashes in my native code with no message whatsoever. One time, by inspecting the code, I've found out that the problem was there was not enough memory. This time by inspecting the code I see nothing. Is there though a common approach for such cases? How should I approach the problem? Sometimes it crashes with 'invalid address at 0xdeadbad' sometimes it prints an (NDK) stack trace but I really don't know what to do with it.

Try http://stackoverflow.com/questions/11435076/where-can-we-download-previous-revisions-of-the-android-support-library — Alexander Kulyakhtin, Sep 20 '12 at 17:52

score 1 · Answer 1 · edited May 23 '17 at 12:03

1

See How to use addr2line in Android - the answers explain how you make sense of the crash stack trace.

edited May 23 '17 at 12:03

Community

1
1

answered Sep 20 '12 at 00:27

Alex Cohn

56,089
9
113
307

score 1 · Answer 2 · edited May 23 '17 at 12:27

1

Don't rely on reading code to find bugs, it never works. You will end up in changing code that is actually sane, just leading to more bugs...

Use ndk-gdb, it can catch basic problems like SEGFAULT natively without any breakpoint. You have to compile your binaries with debug symbols. Hopefully all the procedure is really simple since the latest releases of the ndk.

edited May 23 '17 at 12:27

Community

1
1

answered Sep 20 '12 at 03:32

m-ric

5,621
7
38
51

My android application crashes in the native layer with no message whatsoever

2 Answers2