Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Jul 2015 18:23:23 +0000
From:      bugzilla-noreply@freebsd.org
To:        chromium@FreeBSD.org
Subject:   [Bug 201543] www/chromium: chrome processes stuck at 100% cpu
Message-ID:  <bug-201543-28929-thHL4rBoJV@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-201543-28929@https.bugs.freebsd.org/bugzilla/>
References:  <bug-201543-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=201543

--- Comment #13 from pete@nomadlogic.org ---
(In reply to Tony Narlock from comment #12)

Hey there - this is the method I'm using to generate a build of chromium with
usable debug symbols.  n.b. - enabling DEBUG in make config does not work, I
have not been able to fix that yet.  The following method should work though:

> uname -ar
FreeBSD pop.rubicorp.com 10.1-RELEASE-p10 FreeBSD 10.1-RELEASE-p10 #0: Wed May
13 06:54:13 UTC 2015    
root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

> cd /usr/ports/www/chromium
> sudo make WITH_DEBUG=yes STRIP=

I let this chug along for a day or so on my 8 core box, then I can run chromium
via gdb like so:
> work/stage/usr/local/share/chromium/chrome-wrapper --gdb

I do not do the "make install" step as I still need to have a non-debug version
on my system.  I'll go ahead and put this info in 196770 as well.

-- 
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-201543-28929-thHL4rBoJV>