New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 597343 link

Starred by 2 users
Status: Fixed
Owner:
█ xunji...@chromium.org
Last visit > 30 days ago
Closed: Apr 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

cr_cronet.py isn't able to symbolicate some native crash dumps

Project Member Reported by xunji...@chromium.org, Mar 23 2016 
Steps to reproduce
1: Add "debug::StackTrace().Print();" somewhere in the code
2: run "cr_cronet.py stack"
3: The stack trace created in Step.1 won't get symbolicated

Proposing to make cr_cronet.py use "third_party/android_platform/development/scripts/stack" instead of "third_party/android_tools/ndk/ndk-stack".  "third_party/android_platform/development/scripts/stack" will correctly symbolicate this type of stack traces.

Something like:
adb logcat -d | CHROMIUM_OUTPUT_DIR=./out/Debug third_party/android_platform/development/scripts/stack
Project Member

Comment 1 by bugdroid1@chromium.org, Apr 8 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3df67ed03b1649c528f4e5be73f2b6f53b10c6e0

commit 3df67ed03b1649c528f4e5be73f2b6f53b10c6e0
Author: xunjieli <xunjieli@chromium.org>
Date: Fri Apr 08 17:02:46 2016

[Cronet] Change cr_cronet.py to use stack wrapper in third_party

BUG= 597343 

Review URL: https://codereview.chromium.org/1859593002

Cr-Commit-Position: refs/heads/master@{#386104}

[modify] https://crrev.com/3df67ed03b1649c528f4e5be73f2b6f53b10c6e0/components/cronet/tools/cr_cronet.py

Comment 2 by xunji...@chromium.org, Apr 8 2016

Owner: xunji...@chromium.org
Status: Fixed (was: Available)
►

Sign in to add a comment