Hi, you can get  crash log from logcat or tombstone, and paste it after type 
stack cmd.
Also, --help will be usefull.

The stack usually looks like:
04-13 08:47:11.356: I/DEBUG(180): stack:
04-13 08:47:11.356: I/DEBUG(180):          7e2e5a98  00000000
04-13 08:47:11.356: I/DEBUG(180):          7e2e5a9c  765d0d49  
/data/app-lib/org.xwalk.core.xwview.shell-2/libxwalkcore.so
04-13 08:47:11.356: I/DEBUG(180):          7e2e5aa0  75893607  
/data/app-lib/org.xwalk.core.xwview.shell-2/libxwalkcore.so
04-13 08:47:11.356: I/DEBUG(180):          7e2e5aa4  7e538fa8  
[anon:libc_malloc]
04-13 08:47:11.356: I/DEBUG(180):          7e2e5aa8  00000000
04-13 08:47:11.356: I/DEBUG(180):          7e2e5aac  90357b60  
[anon:libc_malloc]
04-13 08:47:11.356: I/DEBUG(180):          7e2e5ab0  8fc96408  
[anon:libc_malloc]
04-13 08:47:11.356: I/DEBUG(180):          7e2e5ab4  75893623  
/data/app-lib/org.xwalk.core.xwview.shell-2/libxwalkcore.so
04-13 08:47:11.356: I/DEBUG(180):          7e2e5ab8  75893607  
/data/app-lib/org.xwalk.core.xwview.shell-2/libxwalkcore.so
04-13 08:47:11.356: I/DEBUG(180):          7e2e5abc  7e2e5af4  [stack:6220]
04-13 08:47:11.356: I/DEBUG(180):          7e2e5ac0  7e2e5b00  [stack:6220]
04-13 08:47:11.356: I/DEBUG(180):          7e2e5ac4  8fbd7ba8  
[anon:libc_malloc]
04-13 08:47:11.356: I/DEBUG(180):          7e2e5ac8  8ff6ae08  
[anon:libc_malloc]
04-13 08:47:11.356: I/DEBUG(180):          7e2e5acc  75abb423  
/data/app-lib/org.xwalk.core.xwview.shell-2/libxwalkcore.so
04-13 08:47:11.356: I/DEBUG(180):          7e2e5ad0  7e2e5af4  [stack:6220]
04-13 08:47:11.356: I/DEBUG(180):          7e2e5ad4  75abb43f  
/data/app-lib/org.xwalk.core.xwview.shell-2/libxwalkcore.so
04-13 08:47:11.366: I/DEBUG(180):     #00  7e2e5ad8  7821b738  [anon:libc_malloc


From: 蒋鲲鹏 [mailto:[email protected]]
Sent: Friday, May 29, 2015 4:38 PM
To: Xu, Xing
Cc: [email protected]; 
[email protected]
Subject: Re:RE: [Crosswalk-help] How Can get full crash stack trace in release 
build??

    Xu xing, Thanks for you  advice;
    Yes, I have whole source code of crosswalk;
    but , this tool 
(src/third_party/android_platform/development/scripts/stack) need a input,
    how can i get a correct crash file for the input?



--
feiniao2000([email protected]<mailto:[email protected]>)

At 2015-05-29 16:02:27, "Xu, Xing" 
<[email protected]<mailto:[email protected]>> wrote:

Hi,  If you have all the source code of crosswalk, you can try this command:
src/third_party/android_platform/development/scripts/stack

From: Crosswalk-help 
[mailto:[email protected]<mailto:[email protected]>]
 On Behalf Of 蒋鲲鹏
Sent: Friday, May 29, 2015 3:44 PM
To: 
[email protected]<mailto:[email protected]>;
 
[email protected]<mailto:[email protected]>
Subject: [Crosswalk-help] How Can get full crash stack trace in release build??

Hi, CrossWalk Teams:
    I'm  use xwalk in  my android brower, and find the libxwalkcore.so(Release 
build) has been  crashed,
    and the crash backtrace in tombstone files, only two line;
   How can I get a full crash back stack trace?
                   Thanks!


--
feiniao2000([email protected]<mailto:[email protected]>)


_______________________________________________
Crosswalk-help mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help

Reply via email to