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

Issue 814424 link

Starred by 1 user
Status: Verified
Owner:
█ yunlian@chromium.org
Last visit > 30 days ago
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug
Build-Toolchain



Sign in to add a comment

regression-test: debug sections should be smaller than 4GB in ELF32

Project Member Reported by laszio@chromium.org, Feb 21 2018 
Neither compiler nor linker check this. To avoid surprises, we need a test in the waterfall.
Project Member

Comment 1 by bugdroid1@chromium.org, Feb 23 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/af6116340a86640d8af5deef7d15be84d0d34f59

commit af6116340a86640d8af5deef7d15be84d0d34f59
Author: Yunlian Jiang <yunlian@chromium.org>
Date: Fri Feb 23 11:36:43 2018

chromeos-chrome: check debug file size for arm.

ARM elf32 has 4GB size limit. Some times we get over this
limit unnoticed.  This causes problems like being unable to
symbolize stack trace and so on.
This CL adds a check for that.

BUG= chromium:814424 
TEST=crostryjob kevin-chrome-pfq-tryjob caroline-chrome-pfq-tryjob
     emerge-kevin chromeos-chrome fails with a smaller threshold.

Change-Id: I66a55d187ea3a6b031a7a5b675d4d670aa4be1b8
Reviewed-on: https://chromium-review.googlesource.com/930235
Commit-Ready: Yunlian Jiang <yunlian@chromium.org>
Tested-by: Yunlian Jiang <yunlian@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/af6116340a86640d8af5deef7d15be84d0d34f59/chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild

Comment 2 by yunlian@chromium.org, Feb 23 2018

Status: Verified (was: Untriaged)
►

Sign in to add a comment