From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 8666B138626 for ; Wed, 23 Jan 2013 16:00:13 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 79BE621C0EC; Wed, 23 Jan 2013 15:59:35 +0000 (UTC) Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E410D21C0E6 for ; Wed, 23 Jan 2013 15:59:28 +0000 (UTC) Received: by mail-oa0-f41.google.com with SMTP id k14so8583151oag.28 for ; Wed, 23 Jan 2013 07:59:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=rPup2iNawnZQRt6EL/XjI9M2a5+lBGO+dVi2BfzC49A=; b=AKoen6LCNw3fr9cZnHXeZFlrsBL/JQ/aPhTcZkZPJHsmjUCUOy8GrKvKjY6vRxY138 3asBf0W2bLyJSl7oQS58pc6lEEAk+k5LlB5MI7xx/I5c+6zM0QMFWP+soQkj9RBKeICi ssjDbjvTaLqVrfHLhYSs7bkdQ1SbenwanEoQJzTbkqO8pBPOF/dJu+NbmVl8hHj72Zcn 0j/B2Me7N7CSPcMVqFCGOm1yo5N0DWujbUZt/LKWweTTQoYapOkBRwsxwR7rLhUMQkac k2n/TmqGik9AW3vjqA26lNObVyo1EjkandQFpaxC7P1eQdYZQKajn4RKOFl3iBr6mC53 xFkw== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.60.30.201 with SMTP id u9mr1429825oeh.28.1358956763048; Wed, 23 Jan 2013 07:59:23 -0800 (PST) Received: by 10.76.20.243 with HTTP; Wed, 23 Jan 2013 07:59:22 -0800 (PST) In-Reply-To: <51000735.3060103@nileshgr.com> References: <51000735.3060103@nileshgr.com> Date: Wed, 23 Jan 2013 10:59:22 -0500 Message-ID: Subject: Re: [gentoo-user] libv8 segfault From: Michael Mol To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 6d219ed2-e9fd-400a-a611-79e9cdb39147 X-Archives-Hash: feda762dd101dfbcb68f97ac74a25c1b On Wed, Jan 23, 2013 at 10:52 AM, Nilesh Govindrajan wrote: > I tried compiling all versions of chromium (-O3, but it always worked > previously) & v8 (tried -O3 & -O2 too) > but it always segfaults when I try to open the settings page. > > CrRendererMain[6059]: segfault at 500000000 ip 00007f0d0834970c sp > 00007fff71d91a60 error 4 in libv8.so.3.15.11[7f0d08181000+45d000] > > Quite interestingly, the binary version of chrome works without hitches, > which I don't want to run because I'm a little paranoid about it ;-) > And that also means that there is no hardware fault. > > dev-lang/v8-3.15.11.5 > www-client/chromium-24.0.1312.56 (I'm at present using the google chrome > beta, but chromium 25 doesn't work either). > > Flags: > CFLAGS="-O3 -march=core2 -mtune=core2 -msse -msse2 -mssse3 -mmmx -pipe" > CXXFLAGS="${CFLAGS}" > LDFLAGS="-Wl,-O1 -Wl,--as-needed" > > Just replace that O3 with O2 for v8. > > Anybody knows what's going on here? What USE flags are enabled for chromium? You haven't specified that you're using the custom-cflags USE flag, so whatever's in your global CFLAGS setting is largely irrelevant. Also, you don't need to specify --as-needed; that's default, now. I don't know what those other flags are doing. Start with revdep-rebuild, see if that fixes it. If not, you probably ought to re-emerge chromium and its direct dependencies. Given your recent experience with overclocking and the rather correct warnings about silent data corruption, you may need to re-emerge a lot more than that. -- :wq