Date: Fri, 19 Jun 2015 14:12:06 +0000 From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 196770] www/chromium does not run if built with DEBUG option 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196770-28929-KXNdU8dDn7>