commit | 36ec81ca5727ec8aa4b6d0a15eb24403ac4be59b | [log] [tgz] |
---|---|---|
author | Scott Graham <scottmg@chromium.org> | Thu Jun 22 17:14:52 2017 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Jun 22 18:00:26 2017 |
tree | 9e44ff0b57493b0e82bc84c5e8b4a6db6a2f4fe8 | |
parent | 6f5c7c009849f0942a2cd0ad5b5628eada0749a2 [diff] |
fuchsia: get symbolized backtraces Removes the attempted manual in-process printing of stack traces in favour of letting the system crashlogger print one to stdout and then filtering that in the run script to get file/line info. It does not yet resolve kernel/system symbols, only those in the test binary, but I think that's OK for now. (I started trying to do this all in-process https://chromium-review.googlesource.com/c/544108/1/base/debug/stack_trace_fuchsia.cc but it was getting out of hand, and there was still quite a lot more code required. Using the system one for debug backtraces seems better anyway.) Example output: https://gist.github.com/sgraham/d9d332de986c1caa5dc2644ab9c5191a Bug: 706592 Change-Id: Ic5e6241544d4e38b46db04d4c29f584f316c26b5 Reviewed-on: https://chromium-review.googlesource.com/544109 Reviewed-by: Nico Weber <thakis@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#481600} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: f51fbcd2367c3d4d5f91ca8bf37b76eda60f4da0