I have built Google breakpad as ndk-build build system with -g option.
I have downloaded dump_syms and minidump_stackwalk tools from location.
But when i tried to open minidump on my Linux machine it provide me output as
016-05-31 15:06:33: minidump.cc:4518: INFO: Minidump closing minidump
Operating system: Android
0.0.0 Linux 3.10.57+ #1 SMP PREEMPT Tue Jul 7 11:02:04 CST 2015 armv7l
CPU: arm
ARMv7 ARM part(0x4100c070) features: swp,half,thumb,fastmult,vfpv2,edsp,thumbee,neon,vfpv3,tls,vfpv4,idiva,idivt
4 CPUs
Crash reason: SIGABRT
Crash address: 0x402d
Thread 68 (crashed)
0 libc.so + 0x3d524
r0 = 0x00000000 r1 = 0x0000424a r2 = 0x00000006 r3 = 0x00000000
r4 = 0x9ecd7dd8 r5 = 0x00000006 r6 = 0x00000058 r7 = 0x0000010c
r8 = 0xb7c94158 r9 = 0xb7c93d80 r10 = 0x00000000 r12 = 0x0000424a
fp = 0x9ecd754c sp = 0x9ecd7490 lr = 0xb6e34db5 pc = 0xb6e5b524
Found by: given as instruction pointer in context
1 libc.so + 0x179c9
sp = 0x9ecd74a8 pc = 0xb6e359cb
Found by: stack scanning
2 libc.so + 0x1416b
sp = 0x9ecd74b0 pc = 0xb6e3216d
Found by: stack scanning
3 test.so + 0x114dd6
sp = 0x9ecd74cc pc = 0xa3566dd8
Found by: stack scanning
4 test.so + 0x11483e
sp = 0x9ecd74d4 pc = 0xa3566840
Found by: stack scanning
5 libc.so + 0x124f2
sp = 0x9ecd74d8 pc = 0xb6e304f4
Found by: stack scanning
6 libc.so + 0x154a1
sp = 0x9ecd74e0 pc = 0xb6e334a3
Found by: stack scanning
7 libc.so + 0x4ae3a
sp = 0x9ecd74e4 pc = 0xb6e68e3c
Found by: stack scanning
8 libc.so + 0x141ef
sp = 0x9ecd74f0 pc = 0xb6e321f1
Found by: stack scanning
9 libc.so + 0x4ae3a
sp = 0x9ecd74f4 pc = 0xb6e68e3c
Found by: stack scanning
10 test.so + 0x11483e
sp = 0x9ecd74f8 pc = 0xa3566840
Found by: stack scanning
I am doing something wrong but did not able to figure it out. to generate sym file i followed below procedure.
$dump_syms $PROJECT_PATH/obj/local/$ABI/test.so > test.so.sym
$head -n1 test.so.sym
$mkdir -p symbols/test.so/4DFCDE88787D852DABC1146F1C68406D0
$mv test.so.sym symbols/test.so/4DFCDE88787D852DABC1146F1C68406D0
$ minidump_stackwalk xxxx.dmp /symbols
--
You received this message because you are subscribed to the Google Groups "google-breakpad-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-breakpad-d...@googlegroups.com.
To post to this group, send email to google-brea...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-breakpad-discuss.
For more options, visit https://groups.google.com/d/optout.
we just noticed in CrOS that building w/clang/llvm defaults to newer dwarf than breakpad supports.what was the exact command used to build test.so and other programs ?-mike
I think what's happening is that the test.so file that you are passing to dump_syms is stripped.You need the unstripped .so with debug symbols (which typically is NOT what ends up on the device).
I think what's happening is that the test.so file that you are passing to dump_syms is stripped.You need the unstripped .so with debug symbols (which typically is NOT what ends up on the device).
XXX/obj/local/armeabi-v7a$ ~/dump/dump_syms test.so > test.symXXX/obj/local/armeabi-v7a$head -n1 test.symXXX/obj/local/armeabi-v7a$mkdir -p ./symbols/test/4DFCDE88787D852DABC1146F1C68406D0XXX/obj/local/armeabi-v7a$mv test.sym ./symbols/test/4DFCDE88787D852DABC1146F1C68406D0XXX/obj/local/armeabi-v7a$~/dump/minidump_stackwalk xxxx.dmp ./symbols
please let me know if i am doing something wrong.
complete decoded dump file is attached.