Vscode-cmake-tools: Unable to automatically determine debugger corresponding to compiler

Created on 11 Nov 2019  路  1Comment  路  Source: microsoft/vscode-cmake-tools

Brief Issue Summary

I build my C++ code with CMake tools without any problem. However, when I try to debug the code, it output this:

[build] Starting build
[proc] Executing command: /usr/local/bin/cmake --build /home/myname/build --config Debug --target CUDA_test -- -j 42
[build] ninja: no work to do.
[build] Build finished with exit code 0
[debugger] Unable to automatically determine debugger corresponding to compiler: {}
[main] Failed to generate debugger configuration

If I use the "CMake: run without debugging" option, then everything works as expected. So I guess the link to the debugger is broken?

Expected:

  1. Launch the debugger for the selected target.
  2. Start debugging session.

Apparent Behavior:

  1. Launch the debugger for the selected target.
  2. [debugger] Unable to automatically determine debugger corresponding to compiler: {}

Platform and Versions

  • Operating System: Ubuntu 16.04(SSH)
  • CMake Version: 3.15
  • VSCode Version: 1.40.0
  • CMake Tools Extension Version: 1.2.1
  • Compiler/Toolchain: GCC 5.5.0/Clang 6.0.0

Other Notes/Information

I used to run the process without problem. But then I install Anaconda for Python development(and maybe other processes), and now I can't use CMake debug.
Sorry for such a beginner question, but I can't seems to find a similar question online.
Thank you in advance!

debulaunch bug duplicate

Most helpful comment

>All comments

Was this page helpful?
0 / 5 - 0 ratings