I am trying to allow my project to allow its users to debug the JavaScript scripts they send. I create an inspector and a websocket server on the fly once a user requests to debug a script. It works well but only for the first time. This first time, the "Debugger.scriptParsed" message is sent to the client containing all the necessary data for the remote debugger to render the code and allow the user to interact with it. However, when I perform the same magic again, the message isn't sent anymore, and the remote debugger (vscode or chromium) doesn't get anything useful from the server. I had to work this around by recompiling the code every single time a user wanted to debug it. I don't think this is the best approach, and I think something is wrong either with my understanding of how it works or there is simply a bug or an overlook that took place.
My current understanding is that once an inspector is created, it attaches itself to the V8Platform and sets hooks onto the events, such as when a script is compiled. Once it is compiled, it stores it within its state, and if it is the first occurrence of such an event, it sends it to the remote debugger client. However, it doesn't send these events after it had sent them the first time, as nothing has been compiled since. Is there a way to create an inspector once and compile a script once to let the remote debugger work properly? -- -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/6c63d4dc-1745-4216-8379-9f8d80d1af57n%40googlegroups.com.
