Actually there is some screw up with security tokens. We set the security token of the debug context to the newly created context. However, when d8's REPL has two contexts: an evaluation context and a utility context. Because we initialize the utility context for REPL, the security token of the debug context is now different from that of the evaluation context.
I don't think we really need a utility context. I'll remove it. On Thursday, March 31, 2016 at 7:14:45 AM UTC+2, Ben Noordhuis wrote: > > On Wed, Mar 30, 2016 at 11:17 PM, Deepak Mohan <[email protected] > <javascript:>> wrote: > > Hi, > > > > Accessing into exposed debug object returns type error. Verified with a > few > > versions, not sure if this is a known bug or has the behavior been > changed. > > > > v4.6.85 - Works > > v4.7.80 - Error > > v4.9.385 - Error > > > > ❯ out/Debug/d8 --expose_debug_as=v8debug > > ⏎ > > V8 version 5.1.0 (candidate) > > d8> v8debug > > d8> v8debug.Debug > > (d8):1: TypeError: no access > > v8debug.Debug > > ^ > > TypeError: no access > > at (d8):1:8 > > > > > > Thanks, > > Deepak > > The behavior changed. You have to install a debug event listener with > `v8debug.Debug.setListener()` first now before other functionality > becomes available (including its toString() method, it looks like.) > -- -- 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.
