node --inspect ignores debugger statements and breakpoints inside vm.runInContext

[clarabstract]

• Version: 7.73
• Platform: Windows (10, 64bit)
• Subsystem: v8-debug (?)

The chrome-devtools:// view correctly displays the console output, is aware of the files being executed using vm.runInContext (with filename set), even lets me set breakpoints in them, it just doesn't actually break for them.

I forward the outer console object into the vm context so console.log statements get correctly printed out by the inspector and I can dig through objects, assign them etc. (though it crashes when accessing certain objects - by the looks of it, it doesn't keep a GC reference to them so they are probably just no longer there).

I'm hoping there is a similar mechanism I can use to have the VM's debug context share the outer one?

[richardlau]

cc @nodejs/diagnostics

[eugeneo]

There is a pull request that is trying to address this: #7593

Currently this is all blocked on old debugger getting deprecated/disabled - then we will be able to enable the inspector sooner and track all VM contexts. I will assign this issue to me for now.

[clarabstract]

Thanks!
Is using the old debugger going to work for the time being? (and is that node debugger or node --debug?)

Alternately, what's the last version where it would work?

[eugeneo]

I do not know if --debug supports multicontext.

node debug is a CLI debugger that uses --debug as a protocol.

[xtaltas]

--debug works most of the time to debug context as long as you set "debugger" instructions within the code executed in the context. But it is not a very efficient protocol to debug Promises. It would be great if it could be fixed. Anyway we can help?

[eugeneo]

This issue a dublicate of #7593

[Trott]

Did #14465 solve this?

[jkrems]

Verified that in node 8.4.0 the following breaks as expected:

node --inspect-brk -e 'vm.runInNewContext("const obj = { log: console.log };\nobj.log(1);\ndebugger;\nobj.log(2);", { console })'

I think this is good to close.