Expose debug status

[fabiospampinato]

I've made an extension that puts a debugger into the statusbar, in order to workaround a year-old issue with the default floating debugger widget (#2513 #9093) but I cannot quite make it work perfectly because there's no API for getting the status of the debugger.

In order to do that it would be necessary to know:

• if a debug session is currently active
• when it started/stopped
• if code execution is paused

A decent, and maybe more general, starting point might be to expose the switches used in keybindings under the when key, like inDebugMode for instance.

What do you think?

[weinand]

@fabiospampinato Makes sense. We are working on the debug api right now...

[fabiospampinato]

@weinand Great!

[mikeseese]

@fabiospampinato I'm guessing this is what is preventing the issues I created fabiospampinato/vscode-statusbar-debugger#1 and fabiospampinato/vscode-statusbar-debugger#2?

[fabiospampinato]

@seesemichaelj Exactly.

[fabiospampinato]

@weinand Information about compound debugging should be exposed as well, I've got an issue about it (fabiospampinato/vscode-statusbar-debugger#4) which I cannot fix without it.

Can you provide an estimate for when this issue will be resolved?

[arthurchumak]

https://code.visualstudio.com/updates/v1_24#_debug-toolbar-location

[fabiospampinato]

@weinand As there been any progress on this?

[hediet]

You can do this btw. to sniff the communcation between the debug adapter and VS Code.

[EverlastEngineering]

You can have a look at my code for this extention which reveals the debug in the titlebar:

https://github.com/EverlastEngineering/debugInTitlebar/blob/master/package.json

The only thing I wanted and wasn't able to get was whether breakpoints are globally enabled or disabled, but I am able to see status like stopped, paused, initializing, etc.

[fabiospampinato]

You can do this btw. to sniff the communcation between the debug adapter and VS Code.

@hediet I'm a little late to the party but that looks really interesting, thanks for linking to that.

[roblourens]

I think a DebugAdapterTracker will probably be the best bet here