-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remote debugging #25
Comments
I'm actually debug mostly in C++ modules, and never used JS debugger. So I'm afraid I can't help here. There was a related issue: #23 (comment). I've just checked V8 sources (version 5.4) and that Debug class is still there. |
yeah, you have to use the debug class to implement the commands from the I'm making decent progress. I'll shoot you a link when it's a bit more On Thu, Sep 29, 2016 at 1:17 AM, Pavel Medvedev notifications@github.com
|
I made a (5m) movie showing debugging embedded javascript from the chrome debugger. It's not perfect, but it's a pretty cool proof of concept. https://www.youtube.com/watch?v=qkP49-f_eRg |
Cool, thanks for sharing the results :) |
Did you ever do any work on setting up remote chrome debugging? It was removed from v8 a while ago and some projects like node have their own implementations but I don't see anything that seems pluggable into an arbitrary embedded v8 instance.
If not , if you're interested in collaborating on it let me know. It looks like a lot of work. I would probably yse boost::asio for the socket server and then start doing packet traces to see the order of which Jason requests are used by the protocol and implement responses in that order.
The text was updated successfully, but these errors were encountered: