Re: [v8-users] Cannot build V8 with gclient/gn

2018-11-26 Thread Ethin Probst
Also, apparently they patch it, they're using V 7.0.276.38. They also use make-v8.sh on a build machine, I'm guessing, to build it. On 11/26/18, Ethin Probst wrote: > I'm now curious why no one cared to do that? It just doesn't make sense. > > On 11/26/18, Jakob Kummerow wrote: >> Yes, the offic

Re: [v8-users] Cannot build V8 with gclient/gn

2018-11-26 Thread Ethin Probst
I'm now curious why no one cared to do that? It just doesn't make sense. On 11/26/18, Jakob Kummerow wrote: > Yes, the official V8 build instructions don't work on FreeBSD. That's > because nobody cared enough to make it work. Do you? > > You can look at whatever Node is doing to build V8 on Free

Re: [v8-users] Crash in mksnapshot

2018-11-26 Thread madana gopal
Even with latest branch, we are getting the same error. We are using different toolchain from the one given in V8 builds?. Any specific flag or something to add to prevent this crash?. Thanks. Regards, Madan -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group

Re: [v8-users] Cannot build V8 with gclient/gn

2018-11-26 Thread Jakob Kummerow
Yes, the official V8 build instructions don't work on FreeBSD. That's because nobody cared enough to make it work. Do you? You can look at whatever Node is doing to build V8 on FreeBSD -- I believe they have a solution. Feel free to submit a patch to the documentation (via GitHub PR to v8.dev

[v8-users] Cannot build V8 with gclient/gn

2018-11-26 Thread Ethin Probst
I followed the steps on building V8 at https://v8.dev/docs/build and https://v8.dev/docs/source-code, but I'm using FreeBSD and so CIPD isn't supported on FreeBSD. That's a huge problem because i prevents me from building V8 at all. Not to mention it limits me to Python 2.7 when I want to use P

Re: [v8-users] Crash in mksnapshot

2018-11-26 Thread madana gopal
Hi, Below is the trace: # | # Fatal error in ../../src/heap/setup-heap-internal.cc, line 614 | # Debug check failed: std::signbit(roots.minus_zero_value()->Number()). | # | # | # | #FailureMessage Object: 0x75d37074 | C stack trace === | | ./mksnapshot(v8::

[v8-users] Isolate::RequestInterrupt callback not firing on ARM

2018-11-26 Thread 'Konrad Piascik' via v8-users
Hi, I've got some long running JavaScript that I don't expect to end. I am embedding V8 on ARM and want to connect to the debugger. I am able to connect the JavaScript debugger to d8 on OSX by calling isolate->RequestInterrupt. My callback to RequestInterrupt calls session->dispatchProtocolMe

Re: [v8-users] Crash in mksnapshot

2018-11-26 Thread Jakob Gruber
Try a debug build and run mksnapshot in gdb. You'll get a meaningful stack trace there. Have you tried updating to a more recent V8 version? On Mon, Nov 26, 2018 at 2:51 PM madana gopal wrote: > Hi Team, > > I am facing below crash when building V8 (version 6.9.351) for mipsel > platform. > > FA

[v8-users] Crash in mksnapshot

2018-11-26 Thread madana gopal
Hi Team, I am facing below crash when building V8 (version 6.9.351) for mipsel platform. FAILED: gen/embedded.cc snapshot_blob.bin python ../../tools/run.py ./mksnapshot --turbo_instruction_scheduling --embedded_src gen/embedded.cc --embedded_variant Default --random-seed 314159265 --startup_