Date: Thu, 30 Jul 2015 19:29:15 +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-8ldZpKeRAZ@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 #11 from Ed Maste <emaste@freebsd.org> --- > Forgive me, but https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200617 is > lost on me. I'm not experienced enough at this stage to understand what's going > on there. Sorry about that - the issue I encountered in PR 200617 is that building the Chromium port with the DEBUG option resulted in a binary with a .text segment (i.e., the program's code) larger than the default maximum set by the kernel. That is, by default the kernel refuses to load a binary containing over 128MB of code by default, and the DEBUG build of Chromium is too large. I raised PR 200617 because there's no useful user-facing error message for this case -- just something like "abort". You can increase kern.maxtsiz and try running the DEBUG Chromium. -- 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-8ldZpKeRAZ>