Cannot debug on Ubuntu after update

Brief Issue Summary

VSCode updated the plugin to the MS one

I tried launching the debugger. It fails with

[debugger] Unable to automatically determine debugger corresponding to compiler: {}

I tried this with gcc and clang. Same result

I tried manually setting the debugger:

    "cmake.debugConfig": {
        "type": "GDB",
        "debuggerPath": "/usr/bin/gdb"
    }

Same result

CMake Tools Log

2019-11-08T07:45:56.718Z [debug] [cache] Reading CMake cache file /home/bstanimirov/prj/my/app-server/build/CMakeCache.txt
2019-11-08T07:45:56.723Z [debug] [cache] Parsing CMake cache string
2019-11-08T07:45:56.732Z [warning] [debugger] Unable to automatically determine debugger corresponding to compiler: {}
2019-11-08T07:45:56.732Z [debug] [main] Debug configuration from cache: null
2019-11-08T07:45:56.732Z [error] [main] Failed to generate debugger configuration
2019-11-08T07:45:56.733Z [debug] [extension] [8248] cmake.debugTarget finished (returned null)
2019-11-08T07:45:56.746Z [debug] [cache] Reading CMake cache file /home/bstanimirov/prj/my/app-server/build/CMakeCache.txt
2019-11-08T07:45:56.747Z [debug] [cache] Parsing CMake cache string

[bobbrow]

I have a fix for this in PR. There was an update to the regular expression that mapped compilers to the debugger that caused this regression.

You can workaround this until we release an update by opening ~/.vscode/extensions/ms-vscode.cmake-tools-1.2.1/dist/main.js and replacing line 27378:

  const gcc_compiler_regex = /([cg]\+\+|g?cc)(?=\.exe$|$)/gi;

with

  const gcc_compiler_regex = /([cg]\+\+|g?cc)(?=[^\/\\]*$)/gi;

[andreeis]

I opened a new issue from your last comment. I have a suspicion in the implementation.