I wasn't keeping track of the correct execution context.. once I fixed that, things started working as expected.
On Thursday, October 6, 2016 at 3:25:39 AM UTC-7, Ben Noordhuis wrote: > > On Wed, Oct 5, 2016 at 2:54 PM, Zac Hansen <[email protected] <javascript:>> > wrote: > > I'm really getting the feeling I'm not doing this debugging work right. > > > > I'm spending a lot of time "grepping" out values from the javascript > objects > > in EventDetails into c++, then basically using printf to create some > > javascript code using those values to call into the debug.js code to do > what > > I want. > > > > Is this a "good" way to do stuff or is there a better approach? > > > > --Zac > > If it helps, I pieced it together by reading src/debug and > src/runtime/runtime-debug.cc and going over the tests in > test/mjsunit/debug-*.js and test/cctest/test-debug.cc. > > I mentioned it up-thread but putting together a working prototype in > JS first will save you oodles of time and frustration. > -- -- 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.
