From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-144655-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id CFD72138626
for <garchives@archives.gentoo.org>; Wed, 23 Jan 2013 16:11:40 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id B0A3821C0E0;
Wed, 23 Jan 2013 16:11:25 +0000 (UTC)
Received: from mail-oa0-f50.google.com (mail-oa0-f50.google.com [209.85.219.50])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 12A3821C06D
for <gentoo-user@lists.gentoo.org>; Wed, 23 Jan 2013 16:11:23 +0000 (UTC)
Received: by mail-oa0-f50.google.com with SMTP id n16so8492353oag.23
for <gentoo-user@lists.gentoo.org>; Wed, 23 Jan 2013 08:11: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=js9mXwplUCbKP/XBc6g2jAXOxbrKfH+apGiPfmGzzY0=;
b=FCA+aG4GAgomkW+BO+d6gixfsJamFuJqDJaBiWC6Y/oP47mom7IF8zi5ISolGIdrAJ
36Rpzhc0Latjb86A81RKrPibql6oH2MldTy7/1SJs5gqwQIJ+Mnl2TPaA9v1Fn8my2jT
kcQeFLL6uuWfASZ9UQwziPHExEhQKyu6BvDj7g2+qE0j2SrT6lcgFF1GUixkG0HJOckS
uzYQ0RYo9Aa3g7ORGjmy/CE2PQnf5zNzz/vVSRZiucu9VLbgK7cPhGqxJSAg6LLnwRfk
M9DyHlMDdB3jSvMD1p6BQx5h18VQh5U6APET9hCzKtWiDuUOLwmTVpGTxm2tSWGHmidT
KtcQ==
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
X-Received: by 10.60.12.103 with SMTP id x7mr1455509oeb.56.1358957483119; Wed,
23 Jan 2013 08:11:23 -0800 (PST)
Received: by 10.76.20.243 with HTTP; Wed, 23 Jan 2013 08:11:23 -0800 (PST)
In-Reply-To: <51000AA9.1050603@nileshgr.com>
References: <51000735.3060103@nileshgr.com>
<CA+czFiCDpzGh-2FSsfhq1+emhiyC0HpD-bLR9TOHGCjaYxir2w@mail.gmail.com>
<51000AA9.1050603@nileshgr.com>
Date: Wed, 23 Jan 2013 11:11:23 -0500
Message-ID: <CA+czFiCtsR4jqO-QbbxHcxUoF9kG1PfJz83QrXPt_YSNNhWfbQ@mail.gmail.com>
Subject: Re: [gentoo-user] libv8 segfault
From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Content-Type: text/plain; charset=UTF-8
X-Archives-Salt: 693de9bc-0b0c-4610-b5c7-abf3d1f51fdd
X-Archives-Hash: a454acfc956adce7e078a468f5f08907
On Wed, Jan 23, 2013 at 11:07 AM, Nilesh Govindrajan <me@nileshgr.com> wrote:
> On Wednesday 23 January 2013 09:29:22 PM IST, Michael Mol wrote:
>> On Wed, Jan 23, 2013 at 10:52 AM, Nilesh Govindrajan <me@nileshgr.com> 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
>>
>
> I didn't merge anything while I was playing with overclocking.
> custom-cflags is enabled.
> I found the LDFLAGS on Gentoo Wiki as safe LDFLAGS for optimal
> performance.
Well, then that wiki page is out of date. :)
--
:wq