argh thanks for that Sven.
I didn't see the kHandleZapValue constants, that is useful to know, perhaps
that should be written on the wiki somewhere.
Is there any standard dev/user-generated wiki that this could go into? I
know you guys don't write a lot of documentation but it would be helpful
I guess what threw me was that it doesn't crash if you don't have the 'new'
keyword in the JS ... i wonder why it wouldn't crash then.
On 7 January 2013 16:03, Paul Harris harris...@gmail.com wrote:
argh thanks for that Sven.
I didn't see the kHandleZapValue constants, that is useful to know,
I did at the time, it was internal to v8.
Its the new keyword that seems to cause v8 to crash.
On Friday, December 14, 2012 4:52:04 AM UTC+8, Jakob Kummerow wrote:
Have you tried using your favorite debugger to get a backtrace? That
should help you figure out what's going on.
On Wed, Dec
You return a Handle from a dead HandleScope from Shell::Load. Using a debug
build + gdb can figure this out easily, because we explicitly zap several
data structures with special values to catch such things, in this case it's
kHandleZapValue (0xbaddeaf on ia32).
On Mon, Jan 7, 2013 at 2:11 AM,
Have you tried using your favorite debugger to get a backtrace? That should
help you figure out what's going on.
On Wed, Dec 12, 2012 at 5:41 PM, Paul Harris harris...@gmail.com wrote:
Hello again,
I'm seeing a crash that seems a bit strange.
I adjusted d8.cc's Load method so that it
Hello again,
I'm seeing a crash that seems a bit strange.
I adjusted d8.cc's Load method so that it returns the result of the script
execution, like so:
HandleValue Shell::Load(const Arguments args) {
HandleScope handle_scope;
String::Utf8Value file(args[0]);
if (*file == NULL) {
