New issue
Advanced search Search tips

Issue 744702 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

need to add a unittest on debug symbols.

Project Member Reported by yunlian@chromium.org, Jul 17 2017

Issue description

We need to add some unittest to ensure the debug symbols (google-breakpad) does not break.

The goal of the unittest is to catch some errors like
https://bugs.chromium.org/p/chromium/issues/detail?id=743078
https://bugs.chromium.org/p/chromium/issues/detail?id=710605


Some ideas:
get the symbol files from the debug files. After that, we need
to try to get the function information to make sure we have correct
class names, line numbers and so on?
 
Labels: -Pri-3 Pri-2
Owner: yunlian@chromium.org
Status: Assigned (was: Untriaged)
lets put some priority to this and include unit test for the most recent case to verify that we are generating dwarf-2. 
Components: Infra

Comment 4 by mmoss@chromium.org, Jan 2 2018

Components: -Infra Infra>Client>ChromeOS
[It appears that a bunch of old cros issues bulk-added the "Infra" component recently, but they should probably be "Infra>Client>ChromeOS".]
Components: -Infra>Client>ChromeOS
Components: Tools>ChromeOS-Toolchain
Owner: llozano@chromium.org

Sign in to add a comment