Thanks Kirill Kounik, we are also working on crashes. To identifying these places, I have several suggestions: 1), You may help to file bugs at https://crosswalk-project.org/jira and attach the related logs, specify the detailed version. For release built, there is a script third_party/android_platform/development/scripts/stack can help to generate call stacks. 2), built it from source code. We have created many branches, such as https://github.com/crosswalk-project/crosswalk/tree/crosswalk-18.
Currently the symbol is too big(Several gigabyte) and we have too many version of crosswalk(Including stable/development version), so we didn’t provide these symbols. Regards, Xing From: Crosswalk-help [mailto:[email protected]] On Behalf Of Kirill Kounik Sent: Tuesday, March 15, 2016 5:50 PM To: [email protected] Cc: Sahar Azran <[email protected]> Subject: [Crosswalk-help] Debug symbold for the android embedding library Hi, We are embedding Crosswalk in our Android application. We are using Crashlytics (http://fabric.io/) to track crashes in the application. Certain amount of crashes happen inside Crosswalk native code, and we'd like to start identifying these places. We are not building Crosswalk ourselves so we do not have debug symbols that we need to upload to Crashlytics in order to see descriptive crash information. Is there a way to get debug symbols or debug versions of the native libraries used for Crosswalk for Android? Best Regards, Kirill Kizi app
_______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
