Date: Sat, 04 Jun 2016 22:17:45 +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-ABM3q89KY0@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=3D196770 Arto Pekkanen <aksyom@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aksyom@gmail.com --- Comment #13 from Arto Pekkanen <aksyom@gmail.com> --- (In reply to Ed Maste from comment #11) Just FYI, I've been debugging Chromium to produce core dumps succesfully. However, I never even tried running the debug version of chromium. Instead what I did: - installed www/chromium from packages - separately built the www/chromium port with make build (without installing the port) - located the debug binary (a 4 GB file) in the port working directory - gdb -s <path-to-debug-binary> /usr/local/share/chromium/chrome Like this the gdb loads debug symbols from the debug binary, but runs the actual chrome binary. Works fine. Although I have to say this is an ugly workaround. Would it be possible to strip the debug symbols from the resulting binary, store them in a separate file? --=20 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-ABM3q89KY0>