[v8-users] Building V8 Older versions

Hi, I am very new to v8, by looking at documentation, I could compile the latest version of v8 javascript engine and as well able to write some sample C++ programs. But my requirement is to build version 3.9.24 for x86/x64 Linux platform. I couldn't find any steps and no clue how can I procee

[v8-users] Any way to throw an uncatchable (to javascript) exception from a FunctionTemplate callback function?

I want to be able to stop the current javascript execution when a certain criteria is met from within a C++ function that the triggering javascript cannot catch. I want this information to propagate back to the c++ invoking the code somehow and have the data available to it, though. If I had t

Re: [v8-users] Link error in CentOS 7.2: cannot find -lstdc++

You're querying gcc but your build is using clang. You can disable clang by doing `make x64.debug GYPFLAGS=-Dclang=0` On Wed, Feb 10, 2016 at 11:30 AM, Daniel Brahneborg wrote: > I'm trying to build v8 in Linux, on a quite recent CentOS. > > # cat /etc/centos-release > CentOS Linux release 7.2.

[v8-users] Link error in CentOS 7.2: cannot find -lstdc++

I'm trying to build v8 in Linux, on a quite recent CentOS. # cat /etc/centos-release CentOS Linux release 7.2.1511 (Core) # rpm -q gcc gcc-4.8.5-4.el7.x86_64 # rpm -qa|grep stdc libstdc++-4.8.5-4.el7.i686 libstdc++-devel-4.8.5-4.el7.i686 compat-libstdc++-33-3.2.3-72.el7.x86_64 libstdc++

Re: [v8-users] Re: Exception::Error result is Local

First, I'll confess I'm not a huge fan of MaybeLocal but, leaving that aside, even if I accept the utility of MaybeLocal I would expect it to be used for errors for which there's a reasonable hope of recovery and some way of actually testing the recovery code. If Exception::Error returns an emp

Re: [v8-users] Re: Exception::Error result is Local

Generally, the API tries hard to pass errors up. I wonder if we should return MaybeLocal, then. There's been a huge APi refactoring in the past to deprecate returning empty Locals (or Undefined, or so) as error markers, and instead signal all such failures by returning an empty MaybeLocal. Not qui

[v8-users] Re: Exception::Error result is Local

Thanks for that. I suspected as much. Is v8 really doing embedder's a favor by exposing such a catastrophe to them? Presumably, if Factory::NewError fails, we're out of storage (which v8 correctly doesn't do embedders the favor of exposing to them), there's some other catastrophic failure (like

Re: [v8-users] Finding "--print_opt_code" in memory

On Wed, Feb 10, 2016 at 2:38 PM, D T wrote: > Thanks Jakob, for your answer and sorry for the late response. > > Another thing that came to my mind: Considering I do not execute the JS > code with d8 and the print-opt-code flag but directly within my chrome > browser: > Is the produced code the s

Re: [v8-users] Finding "--print_opt_code" in memory

Thanks Jakob, for your answer and sorry for the late response. Another thing that came to my mind: Considering I do not execute the JS code with d8 and the print-opt-code flag but directly within my chrome browser: Is the produced code the same? Meaning, does it matter, if I execute the JS code

[v8-users] Re: Exception::Error result is Local

This probably never happens, but in case creating the error object fails, undefined is returned. On Monday, February 8, 2016 at 9:03:42 PM UTC+1, Alex Kodat wrote: > > This must have been asked before but can't find an explanation so ... just > curious why Exception::Error et al are declared to

Re: [v8-users] Runtime crash on trying to create a half-meg string

Also, https://github.com/v8/v8/wiki/Release-Process#which-version-should-i-embed-in-my-application . On Wed, Feb 10, 2016 at 12:52 PM, Michael Hablich wrote: > "git checkout -b 4.8 -t branch-heads/4.8" > > See https://github.com/v8/v8/wiki/Getting-Started-with-Embedding for more > information. >

Re: [v8-users] Runtime crash on trying to create a half-meg string

"git checkout -b 4.8 -t branch-heads/4.8" See https://github.com/v8/v8/wiki/Getting-Started-with-Embedding for more information. On Wednesday, February 10, 2016 at 12:02:55 PM UTC+1, Danny Dorfman wrote: > > Hello Jakob, > > Thank you for the quick response. Can you please help me fetch the late

Re: [v8-users] Runtime crash on trying to create a half-meg string

Hello Jakob, Thank you for the quick response. Can you please help me fetch the latest *stable* release? (I can't seem to find the instructions in the V8 docs) D. On Wednesday, February 10, 2016 at 11:36:41 AM UTC+2, Jakob Kummerow wrote: > > Version "3.31" doesn't really exist. Yes we once cre

Re: [v8-users] Runtime crash on trying to create a half-meg string

Version "3.31" doesn't really exist. Yes we once created a branch of that name, but it was abandoned right after because it was in such a bad state that we gave up trying to stabilize it. It was never used in a Chrome stable channel release, which would have been your hint that it's ready for produ

[v8-users] Runtime crash on trying to create a half-meg string

Hello there, I am running with V8 3.31, the debug version, and I get this crash upon allocating a large string: #0 0x7f0a6b0efb4b in v8::base::OS::Abort () at ../src/base/platform/platform-posix.cc:210 210 if (g_hard_abort) { (gdb) bt #0 0x7f0a6b0efb4b in v8::base::OS::Abort () at .