Maybe you are looking for this? src/third_party/android_platform/development/scripts/stack After typing this command, pasting the crash stack, you may get a readable call stack.
Regards, Xing From: Crosswalk-dev [mailto:crosswalk-dev-boun...@lists.crosswalk-project.org] On Behalf Of Rahul Pal Sent: Sunday, September 13, 2015 7:47 AM To: crosswalk-dev@lists.crosswalk-project.org Subject: [Crosswalk-dev] Analyzing Breakpad microdump from crash in libxwalkcore.so Need some help on how to analyze the Breakpad dump, and convert into a readable backtrace. Am trying to analyze a crash in libwalkcore.so, this crash itself happen on cherry-picking a recent commit from chromium into crosswalk-14. Crash gives me a Breakpad Microdump, that is all in hex stack pointers. Tried to follow: https://code.google.com/p/google-breakpad/source/browse/trunk/README.ANDROID Specifically need help on part : III. Getting a stack trace on the host: dump_syms $PROJECT_PATH/obj/local/$ABI/libfoo.so > libfoo.so.sym Doe Not create the symbol file, throws an error : ubuntu@ip-xxxx1:~$ ./dump_syms libxwalkcore.so > libxwalkcore.so.sym libxwalkcore.so: file contains no debugging information (no ".stab" or ".debug_info" sections) Also tried re-building adding (GYP_DEFINES) linux_dump_symbols=1, that too did Not help.
_______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
