Currently, the only thing you can do is to attach a debugger, and see what the exception is that gets thrown.
best -jochen On Tue, Jun 30, 2015 at 3:54 PM Domenic Denicola <[email protected]> wrote: > While messing around with V8 extras, I managed to introduce some malformed > syntax or misused API, which caused V8 context creation to fail during > layout test startup. This manifests in > WebCoreTestSupport::injectInternalsObject being passed an empty > v8::Local<v8::Context>, and a subsequent crash. > > I was wondering if there were some log file or something I could look in, > where V8 would tell me why it failed to create a context? I only was able > to figure out that this was due to my JS work due to some pretty extensive > bisecting. And now I'm in for a fun time commenting out plausible-looking > lines in my V8 extra .js file to find which ones are triggering the crash. > If there were some way to get V8 to say "I failed while compiling this > extra, on line X, because you tried to do bad thing Y," I'd be a very happy > developer. > > -- > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > --- > You received this message because you are subscribed to the Google Groups > "v8-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
