Repository navigation
"Run and Debug" and "F5" doesn't show the compilers detail in the API #4278
Description
Activity
This is fixed in the new build task changes. Will be available in C/C++ Extension Version: 1.1.0
Elaheh Rashedi (@elahehrashedi) I'm still reproing this with 1.1.0-insiders. What's supposed to happen?
4 remaining items
Yeah, it doesn't show the details with vscode-insiders. Use F5 (or Build and Debug Active File).
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: #6376Sean McManus (@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.
- changed the title
[-]Options with duplicate names in the 'Add Configuration' feature[/-][+]"Run and Debug" doesn't show the compilers detail in the API[/+]on Oct 23, 2020 - changed the title
[-]"Run and Debug" doesn't show the compilers detail in the API[/-][+]"Run and Debug" and "F5" doesn't show the compilers detail in the API[/+]on Oct 23, 2020 - locked and limited conversation to collaborators
on Dec 12, 2020
Type: General
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.jsonandtasks.json; option 3 creates a slightly differentlaunch.jsonfile ("miDebuggerPath": "/bin/gdb"instead of"/usr/bin/gdb").In any case, this is confusing.