I am not sure if you provide the whole backtrace.  It seems this related 
cc/input/top_controls_manager.cc.

signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 10572 (v.pluto.android)
pid: 10572, tid: 10572, name: v.pluto.android  >>> tv.pluto.android <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
     r0 9207cc00  r1 00000000  r2 04b4e521  r3 00000000
     r4 9ff35e00  r5 beadef60  r6 9207cc00  r7 00000000
     r8 04b4e521  r9 00000000  sl 00000000  fp a24ce404
     ip 00000000  sp beadef58  lr a1643a2d  pc 00000000

Stack Trace:
  RELADDR   FUNCTION                                                            
         FILE:LINE
  00000000                                                                      
         <unknown>
  00990a2b  cc::TopControlsManager::Create(cc::TopControlsManagerClient*, 
float, float)  …cc/input/top_controls_manager.cc:33 (discriminator 1)




Regards,
Xing

From: Rahul Pal [mailto:ra...@pluto.tv]
Sent: Monday, September 14, 2015 10:10 AM
To: Xu, Xing
Subject: Fwd: [Crosswalk-dev] Analyzing Breakpad microdump from crash in 
libxwalkcore.so

Hi Xing,
Attaching the Breakpad-minidump file, in case you or someone you can suggest, 
can figure out by looking at it,
how it can be parsed. Am assuming we need the symbol file in order to parse it.
Thats why was following this link  
https://code.google.com/p/google-breakpad/source/browse/trunk/README.ANDROID


---------- Forwarded message ----------
From: Rahul Pal <ra...@pluto.tv<mailto:ra...@pluto.tv>>
Date: Sun, Sep 13, 2015 at 6:58 PM
Subject: Re: [Crosswalk-dev] Analyzing Breakpad microdump from crash in 
libxwalkcore.so
To: "Xu, Xing" <xing...@intel.com<mailto:xing...@intel.com>>
Cc: 
"crosswalk-dev@lists.crosswalk-project.org<mailto:crosswalk-dev@lists.crosswalk-project.org>"
 
<crosswalk-dev@lists.crosswalk-project.org<mailto:crosswalk-dev@lists.crosswalk-project.org>>

Thanks Xing,
Tried that , did spit out some info, but not the stack trace was looking for.
Again, the input file for the crash, was a Breakpad-minidump.
Not sure if the 'stack' cmd expected that file-format
Pasting the output:


Searching for native crashes in crash.dmp

Reading Android symbols from 
/mnt/rahul/src/third_party/android_platform/development/scripts/../../../..

Reading Chrome symbols from 
/mnt/rahul/src/third_party/android_platform/development/scripts/../../../..

Using toolchain from 
:/mnt/rahul/src/third_party/android_platform/development/scripts/../../../../third_party/android_tools/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/arm-linux-androideabi-

-----------------------------------------------------

signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 10572 (v.pluto.android)

pid: 10572, tid: 10572, name: v.pluto.android  >>> tv.pluto.android <<<

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0

     r0 9207cc00  r1 00000000  r2 04b4e521  r3 00000000

     r4 9ff35e00  r5 beadef60  r6 9207cc00  r7 00000000

     r8 04b4e521  r9 00000000  sl 00000000  fp a24ce404

     ip 00000000  sp beadef58  lr a1643a2d  pc 00000000

Stack Trace:

  RELADDR   FUNCTION                                          FILE:LINE

  00000000                                                    <unknown>

  00990a2b  cc::TopControlsManager::Animate(base::TimeTicks)  
unwind-dw2-fde-dip.c:?

On Sun, Sep 13, 2015 at 6:07 PM, Xu, Xing 
<xing...@intel.com<mailto:xing...@intel.com>> wrote:
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<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<mailto: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

Reply via email to