Updates:
Cc: a...@chromium.org
Comment #5 on issue 9932 by a...@chromium.org: Linux build dies in V8 on
Fedora 11 beta
http://code.google.com/p/chromium/issues/detail?id=9932
[+cc ager] because the V8 folks might want to look at this.
ager: if you want a Fedora 11 box to test on, emai
Comment #4 on issue 9932 by craig.schlenter: Linux build dies in V8 on
Fedora 11 beta
http://code.google.com/p/chromium/issues/detail?id=9932
When compiled with -O3 and -g, I can get a backtrace for the mksnapshot
segfault btw.:
Program received signal SIGSEGV, Segmentation fault.
0x0812328
Comment #3 on issue 9932 by evan.martin: Linux build dies in V8 on Fedora
11 beta
http://code.google.com/p/chromium/issues/detail?id=9932
I just saw a checkin go by that re-enabled Wall for normal Chromium -- it
got dropped
in the gyp migration. :(
--
You received this message because you
Comment #2 on issue 9932 by craig.schlenter: Linux build dies in V8 on
Fedora 11 beta
http://code.google.com/p/chromium/issues/detail?id=9932
To make it work when compiled for Release:
1. add '-fno-strict-aliasing', around line 172 or so of build/common.gypi
2. remove the stripping of -O2 and
Comment #1 on issue 9932 by craig.schlenter: Linux build dies in V8 on
Fedora 11 beta
http://code.google.com/p/chromium/issues/detail?id=9932
The debug build with gcc 4.4 is fine for me (on fedora 9 but I've updated
gcc and glibc).
nteon did try with -fno-strict-aliasing at some point but I
Status: Assigned
Owner: t...@chromium.org
Labels: Type-Bug Pri-3 OS-Linux Area-BrowserBackend Size-Medium
New issue 9932 by a...@chromium.org: Linux build dies in V8 on Fedora 11 beta
http://code.google.com/p/chromium/issues/detail?id=9932
FC11 is GCC 4.4 based and it looks like we might have is
