New issue
Advanced search Search tips

Issue 792630 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Fuchsia
Pri: 1
Type: Bug



Sign in to add a comment

Symbols from libraries are not correctly symbolized.

Project Member Reported by w...@chromium.org, Dec 6 2017

Issue description

Dyanamic libraries are placed in the bootfs under the lib/ path, for the dynamic loader to find them, so the symbol mapping expects them to be named e.g. 'lib/libbase.so'.

However, the name associated with the DSOs in back-traces is just the library base-name, causing symbolization to fail.

This should be fixed properly, by using the ELF build-Ids (issue 772252), but a quick-fix for this particular case is also desirable.
 

Comment 1 by w...@chromium.org, Dec 6 2017

Components: Internals>PlatformIntegration
Project Member

Comment 2 by bugdroid1@chromium.org, Dec 6 2017

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

commit e8357b1427fe8b9c0bf5b9a989bd0ebb5d96a039
Author: Wez <wez@chromium.org>
Date: Wed Dec 06 22:10:44 2017

Quick-fix library lookup by-name for Fuchsia back-trace symbolization.

Bug:  792630 , 772252
Change-Id: I2cd4ea498cbdd614b3469cf92bd4d7b2ee994b39
Reviewed-on: https://chromium-review.googlesource.com/812209
Reviewed-by: Scott Graham <scottmg@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#522223}
[modify] https://crrev.com/e8357b1427fe8b9c0bf5b9a989bd0ebb5d96a039/build/fuchsia/runner_common.py

Comment 3 by w...@chromium.org, Dec 6 2017

Status: Fixed (was: Started)

Sign in to add a comment