@Colengc Here I stopped showing the debug configurations in which the debugger is invalid in the drop down. And the user will see the warning in the output channel to know that the debug config was being ignored. Is this a good approach?

@sean-mcmanus does this message look good?
('debugger.path.not.exists', "Unable to find the {0} debugger in this path: {1}. The debug configuration for {2} is ignored.", \"${debuggerName}\", \"${debuggerPath}\", compilerName)

@sean-mcmanus does this message look good? ('debugger.path.not.exists', "Unable to find the {0} debugger in this path: {1}. The debug configuration for {2} is ignored.", \"${debuggerName}\", \"${debuggerPath}\", compilerName)

Sure.