Thank you,

That looks like the problem. I fixed it by adding the compiler flag "-
fno-builtin-memcpy"

Could someone with source access put a test in the scons script to set
this compiler option when the gcc version is 4.5.x? The gcc bugzilla
says this fix will be ready in gcc 4.6.

Cheers, James

On Dec 30, 3:27 pm, Vyacheslav Egorov <[email protected]> wrote:
> I think you have encountered the following issue:
>
> http://code.google.com/p/v8/issues/detail?id=884
>
> --
> Vyacheslav Egorov
>
> On Thu, Dec 30, 2010 at 4:06 PM, [email protected] <
>
>
>
>
>
>
>
> [email protected]> wrote:
> > Thanks for responding quickly.
>
> > I'm using gcc 4.5.1.
>
> > When I compile using "mode=debug" then mksnapshot works fine and my
> > code stops freezing.
>
> > mode=release causes the 100% CPU freeze from at least version 2.3.8
> > onwards. Bad code generation using gcc 4.5.1 and -O3 maybe?
>
> > On Dec 30, 2:57 pm, Vyacheslav Egorov <[email protected]> wrote:
> > > What happens when you build debug version of v8?
>
> > > scons arch=x64 shapshot=on mode=debug
>
> > > Which version of GCC you are using?
>
> > > --
> > > Vyacheslav Egorov
>
> > > On Thu, Dec 30, 2010 at 3:54 PM, [email protected] <
>
> > > [email protected]> wrote:
> > > > Hi,
>
> > > > Building v8 on centos 5 using:
>
> > > > scons arch=x64
>
> > > > Any code I link against libv8 now pauses forever at 100% CPU usage
> > > > when I call v8::Context::New()
>
> > > > I tried building with:
>
> > > > scons arch=x64 snapshot=on
>
> > > > This caused the build system to pause forever at 100% CPU running a
> > > > script called "mksnapshot".
>
> > > > Tried this using tags: 2.3.8, 2.5.9.6, branch 2.5 and trunk.
>
> > > > Is there a known issue with libv8 not working on Centos 5/Redhat 5?
>
> > > > --
> > > > v8-users mailing list
> > > > [email protected]
> > > >http://groups.google.com/group/v8-users
>
> > --
> > v8-users mailing list
> > [email protected]
> >http://groups.google.com/group/v8-users

-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users

Reply via email to