Show some better UI hint that a compiler is not available from the dropdown of Debug C/C++ file due to a debugger being missing

[sean-mcmanus]

Via the Debug C/C++ file button I see cl.exe and LLVM clang, but not mingw g++. I see it being added as a known compiler in the TypeScript debugger, but then something is causing it to not get used when it seems like it should be.

UPDATE: I didn't notice the logging logger.getOutputChannelLogger().appendLine(localize('debugger.path.not.exists', "Unable to find the {0} debugger. The debug configuration for {1} is ignored.", "${debuggerName}", compilerName)); -- maybe an "info/hint" entry could be added to the quick pick showing that g++ is potentially available if the user were to install the missing gdb.

[sean-mcmanus]

Ah, it was "by design". There is an error saying "gdb.exe" cannot be found for g++.exe in the C/C++ output pane.

pacman -S mingw-w64-ucrt-x86_64-gdb fixes it.

[bobbrow]

Maybe we should tell the user so that they don't get confused like you did?

[sean-mcmanus]

@bobbrow I'm not sure how that would be exposed/told to the user. The user is already told that in the logging, but I didn't look. Did you have some UI suggestion on how users would be warned of the missing debugger? Is there a way to add a "disabled/warning message" item in the quick pick? I don't remember seeing that done before. I don't think we want a popup to appear.

[bobbrow]

I don't have an idea for this right now, but we could keep the issue open as a feature request. It's possible we could add a set of entries to the drop down for compilers that don't have debuggers associated with them and then follow up with a prompt for a path to the debugger if they select it.