Re: [Crosswalk-dev] [Crosswalk-help] How Can get full crash stack trace in release build??

2015-05-31 Thread 蒋鲲鹏
HI Xu , Thanks for you advice; I modify the file gyp_xwalk from "-Drelease_unwind_tables = 0" to "-Drelease_unwind_tables=1')"; the Release Build libxwalk.so can get whole stack trace like Debug build. -- feiniao2000(jk...@163.com) At 2015-05-29 20:27:11, "Xu, Xing" wrote: Hi, you

Re: [Crosswalk-dev] [Crosswalk-help] How Can get full crash stack trace in release build??

2015-05-29 Thread Xu, Xing
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 04-13 08:47:11.356: I/DEBUG(180): 7e2

Re: [Crosswalk-dev] [Crosswalk-help] How Can get full crash stack trace in release build??

2015-05-29 Thread 蒋鲲鹏
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(jk...@163.com) At 2015-05-29 16:02:27, "Xu,

Re: [Crosswalk-dev] [Crosswalk-help] How Can get full crash stack trace in release build??

2015-05-29 Thread Xu, Xing
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:crosswalk-help-boun...@lists.crosswalk-project.org] On Behalf Of 蒋鲲鹏 Sent: Friday, May 29, 2015 3:44 PM To: crosswalk-dev@lists.cros