android - 最近在测试NDK的时候一直挂在libc

Question

最近在测试NDK的时候发现代码经常挂在libc上面，但是有时候又可以。这个错误又没有指出是那个地方调用导致了错误。毫无头绪

标签TD_NDK是自己打印的日志

01-04 19:27:09.519 I/TD_NDK  (25720): start_init [start_time:1483529229, abi:armeabi, abi_bit:32]
01-04 19:27:09.529 D/dalvikvm(25720): GC_CONCURRENT freed 694K, 27% free 8216K/11112K, paused 4ms+19ms, total 72ms
01-04 19:27:09.529 W/SurfaceFlinger(  127): WARNING: disp 2: connected, non-null list, layers=1
01-04 19:27:09.529 I/brcm-hwc(  127): virtual_display_management: defering composition for virtual display 2...
01-04 19:27:09.529 I/brcm-hwc(  127): update_wfc_scene: Virtual display 2, ignoring WFC scene update
01-04 19:27:09.539 I/TD_NDK  (25720): start_init32 [e_entry:0xd, off:0x16438, size:36152]
01-04 19:27:09.539 F/libc    (25720): Fatal signal 11 (SIGSEGV) at 0x6157b9b3 (code=1), thread 25720 (roid.armdemo304)
01-04 19:27:09.539 F/libc    (25720): Unable to open connection to debuggerd: Connection refused
01-04 19:27:09.539 W/SurfaceFlinger(  127): WARNING: disp 2: connected, non-null list, layers=1

Answer 1

01-04 19:27:09.539 F/libc (25720): Fatal signal 11 (SIGSEGV) at 0x6157b9b3 (code=1), thread 25720 (roid.armdemo304)

When sigsegv appears, it can basically be concluded that it is a pointer problem, an array out of bounds, or an overflow