| 1 |
On Wednesday 23 January 2013 09:22:21 PM IST, Nilesh Govindrajan wrote: |
| 2 |
> I tried compiling all versions of chromium (-O3, but it always worked |
| 3 |
> previously) & v8 (tried -O3 & -O2 too) |
| 4 |
> but it always segfaults when I try to open the settings page. |
| 5 |
> |
| 6 |
> CrRendererMain[6059]: segfault at 500000000 ip 00007f0d0834970c sp |
| 7 |
> 00007fff71d91a60 error 4 in libv8.so.3.15.11[7f0d08181000+45d000] |
| 8 |
> |
| 9 |
> Quite interestingly, the binary version of chrome works without hitches, |
| 10 |
> which I don't want to run because I'm a little paranoid about it ;-) |
| 11 |
> And that also means that there is no hardware fault. |
| 12 |
> |
| 13 |
> dev-lang/v8-3.15.11.5 |
| 14 |
> www-client/chromium-24.0.1312.56 (I'm at present using the google chrome |
| 15 |
> beta, but chromium 25 doesn't work either). |
| 16 |
> |
| 17 |
> Flags: |
| 18 |
> CFLAGS="-O3 -march=core2 -mtune=core2 -msse -msse2 -mssse3 -mmmx -pipe" |
| 19 |
> CXXFLAGS="${CFLAGS}" |
| 20 |
> LDFLAGS="-Wl,-O1 -Wl,--as-needed" |
| 21 |
> |
| 22 |
> Just replace that O3 with O2 for v8. |
| 23 |
> |
| 24 |
> Anybody knows what's going on here? |
| 25 |
> |
| 26 |
|
| 27 |
Looks like I proved myself wrong. The binary version crashed on |
| 28 |
extensions page with a segfault -_- |
| 29 |
|
| 30 |
-- |
| 31 |
Nilesh Govindarajan |
| 32 |
http://nileshgr.com |
Archives