"Run and Debug" and "F5" doesn't show the compilers detail in the API

[ranolfi]

Type: General

• OS and Version: Arch Linux
• VS Code Version: Code-OSS 1.37.1
• C/C++ Extension Version: 0.25.1

When we have a workspace folder open, in the Debug panel when clicking the Add Configuration option and then select C++ (GDB/LLDB), some options with the same name are offered:

I tried all three "g++ build and debug active file". Options 1 and 2 generates the same launch.json and tasks.json; option 3 creates a slightly different launch.json file ("miDebuggerPath": "/bin/gdb" instead of "/usr/bin/gdb").

In any case, this is confusing.

[elahehrashedi]

This is fixed in the new build task changes. Will be available in C/C++ Extension Version: 1.1.0

[sean-mcmanus]

@elahehrashedi I'm still reproing this with 1.1.0-insiders. What's supposed to happen?

[sean-mcmanus]

That screenshot is from F5 with no tasks.json generated.

[sean-mcmanus]

I see it fixed for Configure Default Build Task.

[elahehrashedi]

@sean-mcmanus can you please use the vscode-insiders so that I can see the details of each of those compilers?

[sean-mcmanus]

Yeah, it doesn't show the details with vscode-insiders. Use F5 (or Build and Debug Active File).

[elahehrashedi]

The user is getting this screen after running "Run and debug" or pressing "F5". I fixed this issue and sent a PR.

the paths are not visible:

I solved this problem for "Run and Debug". look at bug: #6376

@sean-mcmanus but when we are running ("C/C++ build and debug active file), the details are not visible and it seems to be on Vs Code side, as the details are being set, but the API doesn't show them. I need to investigate more on this. If the details (i.e. compiler paths) are shown to the user, they will see the difference between different compilers. I opened a new issue for this.