Call native logging APIs when debugging in the extension host

[connor4312]

Currently in extension host debugging, logged messages are placed directly in the Debug Console and bypass js-debug.

However, now (as of microsoft/vscode-js-debug#412) js-debug has the capability to replace paths stacktraces thrown from compiled code with their respective source locations, so there's a compelling benefit to change this behavior. Either to actually call the native APIs (which would be the easiest for me 😄) or implement some custom DAP message to pass the log through the debugger here

vscode/src/vs/workbench/contrib/debug/browser/debugService.ts

Line 144 in cc29a81

this.toDispose.push(this.extensionHostDebugService.onLogToSession(event => {

[weinand]

Since extension debugging is a private feature of VS Code, we can use any mechanism that works...

However, there is the DAPTracker API and we have LiveShare that uses the tracker to do their magic.
So we should always keep this in mind when bypassing anything.

[isidorn]

@connor4312 let me know you would like to tackle this with me? I am flexible.

[connor4312]

Sure. I'm available next week, feel free to send an invite or grab me whenever we're both online.