Re: [v8-users] Any build flag to maintain regular v8 stack trace?

It does. --gdbjit_full gives me the complete stack. Thanks again! On Wednesday, September 28, 2016 at 12:09:52 AM UTC-7, Ben Noordhuis wrote: > > On Sat, Sep 24, 2016 at 2:40 AM, Jane Chen > wrote: > > Thanks, Ben! > > > > I added that flag to my v8 init code. Now I

[v8-users] Re: No libv8.a generated for either X64 or ARM64 build.

In case anyone else would prefer to use static libraries in their own build, I have found it easiest to create all .a files as (thin archives) in the same directory, with cd to .../v8/v8/out/x64/obj and then: ar rcsDT libv8_base.a v8_base/*.o (repeated for each library directory) All

Re: [v8-users] linking error while building V8 for Android device using GN and Ninja

did you install the arm64 sysroot? On Wed, Sep 21, 2016 at 9:33 AM Yakir E wrote: > Hi all, > I am trying in the last few days to build V8 for Android. I am using > Ubuntu 64bit as the build machine. After a lot of tries I was able to make > ninja to start the build but after

[v8-users] Re: How to build V8 on Linux using GCC instead of Clang?

You need this in your args.gn: is_clang=false use_sysroot=false On Wednesday, September 28, 2016 at 2:15:47 AM UTC+2, Ivan P. wrote: > > Amendment: used ninja -v -C out.gn/test1 > So I can see all commands executed in console output, and I can see it > uses clang++. > > среда, 28 сентября 2016

Re: [v8-users] Any build flag to maintain regular v8 stack trace?

On Sat, Sep 24, 2016 at 2:40 AM, Jane Chen wrote: > Thanks, Ben! > > I added that flag to my v8 init code. Now I get: > > 12 xdmp::JSEngine::evalBuiltin() > /space/projects/head/xdmp/src/JSEngine.cpp:11794 0x0391466e > 11 xdmp::JSEngine::evalBuiltin() >