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

Issue 855086 link

Starred by 2 users
Status: Verified
Owner: ----
Closed: Jun 2018
Cc:
█ yunlian@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug
Build-Toolchain



Sign in to add a comment

false alarm on debug file size exceed 4GB

Project Member Reported by yunlian@chromium.org, Jun 21 2018 
We use command 
 files=$(find "${ED}/usr/lib/debug${CHROME_DIR}" -size 4G -o -size +4G)

However, it reports false alarm on a chrome.dwp whose size is

3230812820
Project Member

Comment 1 by bugdroid1@chromium.org, Jun 21 2018 

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

commit 6d8b8777629230662529e056b2e31fec9d13a927
Author: Yunlian Jiang <yunlian@google.com>
Date: Thu Jun 21 23:31:25 2018

chromeos-chrome: fix false alarm on debug size.

We got a false alarm on debug size exceeds 4GB on ARM. This fixes that.

BUG= chromium:855086 
TEST=find -size +$((4 * 1024 * 1024 * 1024 - 1))c does not chrome.dwp anymore.

Change-Id: I34e1ac2ac8d841af3eee7d9a1ffb73b41d9eb24a
Reviewed-on: https://chromium-review.googlesource.com/1110270
Commit-Ready: Yunlian Jiang <yunlian@chromium.org>
Tested-by: Yunlian Jiang <yunlian@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

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

Comment 2 by yunlian@chromium.org, Jun 28 2018

Status: Verified (was: Untriaged)
►

Sign in to add a comment