[v8-users] Re: V8 JSON Debugging Protocol, Breakpoints not being set

I would urge you to use the DevTools protocol instead, used for example in test/inspector/inspector-test.cc The old JSON debug API is deprecated and going to be removed soon. Cheers, Yang On Monday, October 17, 2016 at 11:00:30 PM UTC+2, WIlliam Taylor wrote: > > >

[v8-users] Re: Debugging Javascript in V8

The old debugger protocol is no longer supported. We do support the devtools protocol though. You could take a look at how v8/test/inspector-test.cc works. In your project, you could open a socket to pass devtools protocol messages through to V8, and use Chrome DevTools to debug. If everything

Re: [v8-users] Breaking On Native Function Calls

Yes, I am. I already noticed it is blocking the Chromium issue. Thank you! ☆*PhistucK* On Thu, Oct 20, 2016 at 9:33 AM, Yang Guo wrote: > I guess you are looking for https://bugs.chromium.org/ > p/v8/issues/detail?id=178 > > This is a long standing feature request that

Re: [v8-users] Breaking On Native Function Calls

Yeah, I wish. I do not have a strong machine yet. :( I wanted to try an old version of Chromium (which does not have [Unforgeable] yet), but my corporate proxy is blocking me from using the site in question. I will try again when I am home. ☆*PhistucK* On Thu, Oct 20, 2016 at 9:31 AM,

Re: [v8-users] Breaking On Native Function Calls

I guess you are looking for https://bugs.chromium.org/p/v8/issues/detail?id=178 This is a long standing feature request that has not been addressed yet. I'll add it to our backlog. On Thursday, October 20, 2016 at 7:55:38 AM UTC+2, PhistucK wrote: > > File ​crbug.com/657697​ (and

Re: [v8-users] Breaking On Native Function Calls

If making your own build of Chromium for your investigation purposes makes sense to you, it should work for you to remove "Unforgeable" here: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/frame/Window.idl?l=41 Then, you could defineProperty window.location to your "proxy"