From: Nilesh Govindrajan <me@nileshgr.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] libv8 segfault
Date: Wed, 23 Jan 2013 21:37:05 +0530 [thread overview]
Message-ID: <51000AA9.1050603@nileshgr.com> (raw)
In-Reply-To: <CA+czFiCDpzGh-2FSsfhq1+emhiyC0HpD-bLR9TOHGCjaYxir2w@mail.gmail.com>
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.
--
Nilesh Govindarajan
http://nileshgr.com
next prev parent reply other threads:[~2013-01-23 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 15:52 [gentoo-user] libv8 segfault Nilesh Govindrajan
2013-01-23 15:59 ` [gentoo-user] " Nilesh Govindrajan
2013-01-23 15:59 ` [gentoo-user] " Michael Mol
2013-01-23 16:07 ` Nilesh Govindrajan [this message]
2013-01-23 16:11 ` Michael Mol
2013-01-24 0:15 ` Adam Carter
2013-01-23 17:25 ` [gentoo-user] /proc/net/wirelesslessness ☈king
2013-01-23 20:24 ` Paul Hartman
2013-01-24 11:07 ` ☈king
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51000AA9.1050603@nileshgr.com \
--to=me@nileshgr.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox