[v8-users] Proposal to switch from Unibrow to ICU in V8

Hi V8 users, V8 has its own built-in, custom, minimal Unicode library called Unibrow. I am looking into replacing Unibrow with the ICU library. There would be a fallback for non-ICU builds which supports the UTF-8 and UTF-16 encodings for source code, but only gets operations like case mapping rig

Re: [v8-users] Profiler: Application crash in HandleProfilerSignal

I just confirmed this happens in my app with the same version as the shipping Chrome, 4.7.80.25. Not why this is happening for me and not seen by others. Here's the latest stack crawl: > v8.dll!v8::base::OS::Abort() Line 825 C++ v8.dll!V8_Fatal(const char * file, int line, const char * format,

Re: [v8-users] "Word UnExpected" Error while building v8 on Ubuntu

Hi Rodolph, Thank you so much!!! This works like a charm. V8 team should document this somewhere. I also added werror=no to avoid some warnings became errors because using newer toolchain (Linaro 5.2). ./tools/cross_build_gcc.sh $PREFIX arm.release hardfp=on werror=no -j8 Johnny On Mon, Jan 1

Re: [v8-users] On Android binary segfaults

Maybe check (with file) that the binaries are built for arm. if they are built for arm you can try: export GYPFLAGS="-Dlinux_use_bundled_gold=0" before your build command. I don't build for Android but it is need for linux builds. Rodolph On Mon, 11 Jan 2016 at 18:55 Guillermo Romero wrote: > I

Re: [v8-users] On Android binary segfaults

It also segfaults: root@android:/ # cd /data/local/tmp/v8/out/android_arm.release 130|root@android:/data/local/tmp/v8/out/android_arm.release # unittests -gtest_list_tests [1] + Segmentation fault ./unittests -gtest_list_tests It happens the same with the other binaries built: gato@tigger:~

Re: [v8-users] Profiler: Application crash in HandleProfilerSignal

Any help would be greatly appreciated. Has anyone from google been able to confirm the problem? Is it working for others? On Mon, Dec 14, 2015 at 8:21 AM, Jim Acquavella wrote: > Both my debug and optimized builds are crashing while advancing the > SafeStackFrameIterator > (via SafeStackFrame

Re: [v8-users] Problems with V8::Locker and V8::Debug::DebugBreak

Thanks for your answer Ben. I have just filed my bug. On Saturday, January 9, 2016 at 1:55:29 PM UTC+1, Ben Noordhuis wrote: > > On Fri, Jan 8, 2016 at 2:43 PM, juu > > wrote: > > Hi everyone, > > > > I am having some issues while trying to implement a "wait for debugger" > > feature on my

Re: [v8-users] On Android binary segfaults

from your log it looks like out/android_arm.release/unittests -gtest_list_tests failed can you run the command on its own and see what happens? Rodolph On Sun, 10 Jan 2016 at 20:57 Guillermo Romero wrote: > Hello, > > I'm building V8 for Android (arm), and followed the steps outlined here: > ht

Re: [v8-users] "Word UnExpected" Error while building v8 on Ubuntu

Hi Johnny, When cross compiling for 32-bit arm you need to explicitly prevent the use of the built-in linker. Simply export GYPFLAGS="-Dlinux_use_bundled_gold=0" You don't need the "-DClang=0" if you define CC, CXX and others. The v8 code base already has a script to cross compile, in the tools d

Re: [v8-users] v8 SetWeak callback is not called after context disposal

Garbage collection is not necessarily triggered immediately when you dispose a context. If you rely on freeing the C++ memory right when the context goes out of scope, you can't rely on the GC to trigger at this very moment. best -jochen On Sat, Jan 9, 2016 at 5:01 PM Sergey F. wrote: > Hi Pave