From owner-freebsd-chromium@FreeBSD.ORG  Fri Jun 19 14:12:07 2015
Return-Path: <owner-freebsd-chromium@FreeBSD.ORG>
Delivered-To: chromium@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 2D65C847
 for <chromium@hub.freebsd.org>; Fri, 19 Jun 2015 14:12:07 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 170AA85A
 for <chromium@FreeBSD.org>; Fri, 19 Jun 2015 14:12:07 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t5JEC6g3096377
 for <chromium@FreeBSD.org>; Fri, 19 Jun 2015 14:12:06 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: chromium@FreeBSD.org
Subject: [Bug 196770] www/chromium does not run if built with DEBUG option
Date: Fri, 19 Jun 2015 14:12:06 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: emaste@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: chromium@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: maintainer-feedback?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-196770-28929-KXNdU8dDn7@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-196770-28929@https.bugs.freebsd.org/bugzilla/>
References: <bug-196770-28929@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-chromium@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: FreeBSD-specific Chromium issues <freebsd-chromium.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-chromium>, 
 <mailto:freebsd-chromium-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-chromium/>
List-Post: <mailto:freebsd-chromium@freebsd.org>
List-Help: <mailto:freebsd-chromium-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chromium>, 
 <mailto:freebsd-chromium-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jun 2015 14:12:07 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196770

--- Comment #5 from Ed Maste <emaste@freebsd.org> ---
(In reply to Tony Narlock from comment #4)

> The old revisions claimed there was an "empty binary".
>
> Was that confirmed,

Well, the initial report shows all 0s for hd /usr/local/share/chromium/chrome.
I wouldn't call that an "empty binary," but others might?

In any case, I'm interested in reports of either reproducing a
megabytes-of-zeroes binary, or of building a debug chrome binary that fails to
run (with kern.maxtsiz increased).

I can't reproduce either case, and have added the backtrace that I obtained to
bug #200601. I haven't had any time to look at it, though.

-- 
You are receiving this mail because:
You are the assignee for the bug.