FR support for sourcefile mappings (launch configuration)

[GitMensch]

Often the debugging machine is not identical to the machine that did the compilation (for example the compilation was done via CI, or was done from a version which has later changed and the source that match the debugger are now in a folder "tags") or in case of remote debugging the machine running the process may be a GNU/Linux machine while the machine vscode runs under uses Windows.

I don't know if/how isdbg allows that, but for a debugging extension this commonly this means:

• an optional set of source mappings in the launch configuration (change to package.json for a new attribute)
• honoring the mapping, for example with a mapping of {"/dir1/src", "${workspaceFolder:Source}"} and the debugger telling the current line is "/dir1/src/module1/PROGA.cob" open "${workspaceFolder:Source}/module1/PROGA.cob" and when setting a breakpoint in "${workspaceFolder:Source}/module2/PROGZ.cob" via the UI, tell the debugger to set it in "/dir1/src/module2/PROGZ.cob"

[GustavoASC]

Hi @GitMensch,

I appreciate this issue. It is really interesting and useful.

In this exact moment I am not sure whether isdbg supports this behavior, but I believe it could be implemented on the extension itself (as you suggested) so it may benefit several command-line debuggers in a transparent way. So we don't need to directly modify isdbg ant other external tools in order to support it; a single feature implemented on the extension allows different command-line debuggers to work as expected (I believe).

The extension could translate the UI paths, as you said.