Support multi target debugging

[weinand]

Support multiple debug sessions in a single instance of VS Code.

This helps with the following scenarios:

• debug a client and a server
• debug a clustered program
• debug a multi process application
• debug an extension and its debug adapter and/or language server at the same time

Problems to address:

• multiple debug models or one 'super model'?
• how to launch multiple sessions with a single 'F5'?
• UI: Process view vs. Windows vs. tabs...

[siegebell]

Debugging a language-server & client in one instance would be nice...

[atian25]

+1 for this, maybe we can debug just like webstorm way.

and please consider about auto attach to the new worker since it will be auto reload at development.

and plz also take a look at microsoft/vscode-node-debug#99

[weinand]

The plan is to allow multiple debug sessions in a single VS Code instance. This requires that the debug model/service can be instantiated multiple times. How multiple debug sessions are presented in the UI is an independent issue: probably we will start with something simple, e.g. a simple session switcher or by introducing processes as the top level elements in the call stack view.

[isidorn]

We have added support for mutliple debug sessions. The current way to enable this might change in the future, it is still experimental.

For how to enable compound debugging check #14842

[daviwil]

This is awesome, thanks a lot!

[gerich-home]

How do I know when it will be released?

[isidorn]

@gerich-home #13342

Also this experimental feature is currently available in the vscode insiders

[Gama11]

For anyone stumbling upon this issue via Google (like me), the syntax for compound launch configs has changed since @isidorn's earlier comment. There's a usage example here:

#14842 (comment)

[akoidan]

Also it would be great if there were an ability to switch between target outputs, (atm they are merged):

[weinand]

@Deathangel908 please create a new issue since this issue is already closed.