Hello! I've run into a couple of bugs with the inspector. Collecting them in an issue here. They're all observable with this small modification to the inspector example: https://gist.github.com/f2efc661205307f4b1a9086d751339c8
debugger; works as it should.- Stack seems to work as it should. Variables show up. I can execute code by writing into the console.
- Breakpoints can be set and removed but do not trigger.
- Step Over does not work (acts same as Resume Script Execution)
- Step Into will step to the complicated log's
copyInto statement where it's mapping over the arguments. Very weird!! Other than this weird case Step Into seems to work same as Resume Script Execution. I do not know why the same thing doesn't happen for the simple log implementation. At first I thought it was maybe because copyInto runs code from the default isolate / native, but the simple log's copyInto being skipped disproves that.
Node v 8.11.2
isolated-vm 1.7.7
> uname -srvpoi
Linux 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 GNU/Linux
An aside: I noticed while testing these things out that console.log is defined inside the isolates. It just doesn't log to the "default isolate console". You can see output of console.log when you have an inspector attached to the isolate, if you haven't tried defining it yourself. Comment out / delete the "complicated log" part of the Gist to see this in action.
Hello! I've run into a couple of bugs with the inspector. Collecting them in an issue here. They're all observable with this small modification to the inspector example: https://gist.github.com/f2efc661205307f4b1a9086d751339c8
debugger;works as it should.copyIntostatement where it's mapping over the arguments. Very weird!! Other than this weird case Step Into seems to work same as Resume Script Execution. I do not know why the same thing doesn't happen for the simple log implementation. At first I thought it was maybe becausecopyIntoruns code from the default isolate / native, but the simple log'scopyIntobeing skipped disproves that.Node v 8.11.2
isolated-vm 1.7.7
An aside: I noticed while testing these things out that
console.logis defined inside the isolates. It just doesn't log to the "default isolate console". You can see output ofconsole.logwhen you have an inspector attached to the isolate, if you haven't tried defining it yourself. Comment out / delete the "complicated log" part of the Gist to see this in action.