Debug shows "No compiler found in cache file." dialog #2121

anb0s · 2021-09-12T10:14:35Z

Brief Issue Summary

We are using CMakePresets and configure, build and run (Shift + F5) are working as expected. But using the debug-button shows dialog with only this error: "No compiler found in cache file."

Expected:

The Debug session with builded application is starting or more detailed error is shown to investigate the configuration issue...

Apparent Behavior:

Push the debug-button:

shows dialog with only this error:

"No compiler found in cache file."

CMake Tools Log

main] Building folder: oae.jupiter.s7plcapp 
[build] Starting build
[proc] Executing command: /usr/bin/cmake --build /home/andre/git/oae.jupiter.s7plcapp/build/default
[build] ninja: no work to do.
[build] Build finished with exit code 0
[main] Building folder: oae.jupiter.s7plcapp s7plcapp
[build] Starting build
[proc] Executing command: /usr/bin/cmake --build /home/andre/git/oae.jupiter.s7plcapp/build/default --target s7plcapp
[build] ninja: no work to do.
[build] Build finished with exit code 0

Developer Tools Log

???

Platform and Versions

Operating System: WSL2 with Debian 11 Bullseye (VSCode running @ Windows 10 1909)
CMake Version: 3.21.2
VSCode Version: 1.60.0
CMake Tools Extension Version: 1.8.1
Compiler/Toolchain: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

Other Notes/Information

...

The text was updated successfully, but these errors were encountered:

linquize · 2021-09-12T12:34:12Z

What platform and compiler are you using?

anb0s · 2021-09-12T18:26:25Z

What platform and compiler are you using?

Ah sorry, somehow the description was not saved properly. I've updated the issues description now...

bobbrow · 2021-09-13T16:37:11Z

The debug button at the bottom tries to guess which debugger to use based on information about your compiler found in the CMakeCache.txt and it generates the launch.json information on the fly. If it can't find a CMAKE_CXX_COMPILER or CMAKE_C_COMPILER entry in your cache, it doesn't know where to look to find the debugger and you get this error message.

The workaround is supposed to be to set the debugger yourself in the cmake.debugConfig setting object like this:

"cmake.debugConfig": {
  "MIMode": "gdb",
  "miDebuggerPath": "/path/to/debugger/gdb"
}

But I'm seeing that this error will be thrown just before that setting can override the cache lookup. It should be a quick fix. I'll try to get to it today.

anb0s · 2021-09-14T08:15:37Z

@bobbrow ok, thanks!

I've also tried to configure a launch for this to set debugger etc. like described in the docu:

    {
      "name": "S7 PLC App",
      "type": "cppdbg",
      "request": "launch",
      "program": "${command:cmake.launchTargetPath}",
      "args": [],
      "stopAtEntry": false,
      "cwd": "${workspaceFolder}",
      "environment": [
        {
          // add the directory where our target was built to the PATHs
          // it gets resolved by CMake Tools:
          "name": "PATH",
          "value": "$PATH:${command:cmake.launchTargetDirectory}"
        }
      ],
      "externalConsole": false,
      "MIMode": "gdb",
      "setupCommands": [
        {
          "description": "Enable pretty-printing for gdb",
          "text": "-enable-pretty-printing",
          "ignoreFailures": true
        }
      ]
    },

but receive the error message:

Is it related or shold it work in general with presets?

anb0s · 2021-09-14T08:29:18Z

... If it can't find a CMAKE_CXX_COMPILER or CMAKE_C_COMPILER entry in your cache, it doesn't know where to look to find the debugger and you get this error message.

Just curious: the configuration is done via presets and the folder with cmake cache build/<preset-name> is available (run is working), is there a another logic or reason why the cmake cache is not found?

anb0s · 2021-09-14T09:54:51Z

... If it can't find a CMAKE_CXX_COMPILER or CMAKE_C_COMPILER entry in your cache, it doesn't know where to look to find the debugger and you get this error message.

Just curious: the configuration is done via presets and the folder with cmake cache build/<preset-name> is available (run is working), is there a another logic or reason why the cmake cache is not found?

ok, i think another issue is there, because in the presets we are also using toolchain-files and in the cache it cannot find CMAKE_CXX_COMPILER or CMAKE_C_COMPILER, only this line is there:

//No help, variable specified on the command line.
CMAKE_TOOLCHAIN_FILE:UNINITIALIZED=cmake/toolchains/linux_gcc_x86_64_x32.cmake

Should i create another request for this?

bobbrow · 2021-09-14T16:42:06Z

Do you use set(CMAKE_CXX_COMPILER ... CACHE ...) in your toolchain? (docs) That might fix it.

If that doesn't work, I also built a version of the extension with my proposed fix so you can use the override mechanism. To try it out:

Download the build artifact here: https://github.com/microsoft/vscode-cmake-tools/suites/3767308809/artifacts/92652787
Unzip the VSIX file
Run the "Install from VSIX..." command in VS Code and select the VSIX file

bobbrow · 2021-09-14T16:51:18Z

As for the launch.json error, that's not something I've seen much. The C++ extension shows that message if it thinks it hasn't finished installing its dependencies. You might want to try uninstalling/reinstalling that extension if you continue to see that error.

The updated docs for debugging with launch.json are in our repository. There's a minor edit for the PATH variable that will save you a duplicate build step.

anb0s · 2021-09-14T17:07:24Z

Do you use set(CMAKE_CXX_COMPILER ... CACHE ...) in your toolchain? (docs) That might fix it.

If that doesn't work, I also built a version of the extension with my proposed fix so you can use the override mechanism. To try it out:

Download the build artifact here: https://github.com/microsoft/vscode-cmake-tools/suites/3767308809/artifacts/92652787

Unzip the VSIX file

Run the "Install from VSIX..." command in VS Code and select the VSIX file

Thanks, i've tried the new version of the plugin first.

Added to settings.json file:

 "cmake.debugConfig": {
        "MIMode": "gdb",
        "miDebuggerPath": "/usr/bin/gdb"
    }

Now it shows this output in the console:

[main] Building folder: oae.jupiter.s7plcapp s7plcapp
[build] Starting build
[proc] Executing command: /usr/bin/cmake --build /home/andre/git/oae.jupiter.s7plcapp/build/default --target s7plcapp
[build] ninja: no work to do.
[build] Build finished with exit code 0
[proc] Executing command: /usr/bin/gdb --version

and then the same error dialog like with manually configured launches:

I'm investigating, but have no idea how it's related to install of the plugin, may be something with WSL2...

bobbrow · 2021-09-14T17:16:44Z

It's definitely an issue with the cpptools extension. Did you attempt to reinstall it? If you did and it's still broken, I would recommend opening an issue in that repository. You might be able to get past it by installing the full VSIX from here: https://github.com/microsoft/vscode-cpptools/releases/download/1.6.0/cpptools-linux.vsix. This package includes all of the dependencies as opposed to the one from the VS Code Marketplace which is bare-bones and then downloads the OS-specific dependencies after installation.

anb0s · 2021-09-14T17:31:37Z

Do you use set(CMAKE_CXX_COMPILER ... CACHE ...) in your toolchain? (docs) That might fix it.

FYI: Thanks, now without the entry cmake.debugConfig in settings.xml and adding CMAKE_CXX_COMPILER etc. in toolchains file to the cache the reported error is not shown anymore :) and it executes this:

[build] Build finished with exit code 0
[proc] Executing command: gdb --version

but same error dialog as above with Open 'launch.json' appears...

bobbrow · 2021-09-14T17:36:32Z

Great! The remaining issue has to do with cpptools. If my ideas above didn't work for you, you can open a new issue for it here: https://github.com/microsoft/vscode-cpptools/issues/new/choose.

anb0s · 2021-09-14T17:47:16Z

It's definitely an issue with the cpptools extension. Did you attempt to reinstall it? If you did and it's still broken, I would recommend opening an issue in that repository. You might be able to get past it by installing the full VSIX from here: https://github.com/microsoft/vscode-cpptools/releases/download/1.6.0/cpptools-linux.vsix. This package includes all of the dependencies as opposed to the one from the VS Code Marketplace which is bare-bones and then downloads the OS-specific dependencies after installation.

BIG THANKS 🥇 i was blind ;) That was the issue with WSL2 and not finished cpptools installation! I've used the full pakage and now this error is gone :) and i can debug !!!

anb0s · 2021-09-14T17:50:29Z

The updated docs for debugging with launch.json are in our repository. There's a minor edit for the PATH variable that will save you a duplicate build step.

Yes the parameters in the manual launch config "program": "${command:cmake.launchTargetPath}", and "value": "$PATH:${command:cmake.launchTargetDirectory}" are working, Thanks!

anb0s · 2021-09-14T17:52:29Z

Great! The remaining issue has to do with cpptools. If my ideas above didn't work for you, you can open a new issue for it here: https://github.com/microsoft/vscode-cpptools/issues/new/choose.

All the ideas and the fix from this issues are working, perfect!!!

bobbrow · 2021-09-15T16:40:49Z

Glad to hear that everything is working for you. As an FYI, we just found out that the VS Code Marketplace has finished adding support for platform-specific VSIX packages which means that cpptools will be able to upload the full packages to the Marketplace starting with the next release. This means that you should never have the extension tell you it is still installing starting with v1.7.0.

bobbrow mentioned this issue Sep 13, 2021

reorder some logic in the debugger override case #2123

Merged

bobbrow added Feature: debug/launch fixed (release pending) labels Sep 14, 2021

bobbrow added this to the 1.9.0 milestone Sep 14, 2021

bobbrow closed this as completed Sep 15, 2021

github-actions bot locked and limited conversation to collaborators Jan 29, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Debug shows "No compiler found in cache file." dialog #2121

Debug shows "No compiler found in cache file." dialog #2121

anb0s commented Sep 12, 2021 •

edited

Loading

linquize commented Sep 12, 2021

anb0s commented Sep 12, 2021

bobbrow commented Sep 13, 2021 •

edited

Loading

anb0s commented Sep 14, 2021 •

edited

Loading

anb0s commented Sep 14, 2021 •

edited

Loading

anb0s commented Sep 14, 2021

bobbrow commented Sep 14, 2021

bobbrow commented Sep 14, 2021

anb0s commented Sep 14, 2021

bobbrow commented Sep 14, 2021

anb0s commented Sep 14, 2021

bobbrow commented Sep 14, 2021

anb0s commented Sep 14, 2021

anb0s commented Sep 14, 2021

anb0s commented Sep 14, 2021

bobbrow commented Sep 15, 2021

Debug shows "No compiler found in cache file." dialog #2121

Debug shows "No compiler found in cache file." dialog #2121

Comments

anb0s commented Sep 12, 2021 • edited Loading

Brief Issue Summary

Expected:

Apparent Behavior:

CMake Tools Log

Developer Tools Log

Platform and Versions

Other Notes/Information

linquize commented Sep 12, 2021

anb0s commented Sep 12, 2021

bobbrow commented Sep 13, 2021 • edited Loading

anb0s commented Sep 14, 2021 • edited Loading

anb0s commented Sep 14, 2021 • edited Loading

anb0s commented Sep 14, 2021

bobbrow commented Sep 14, 2021

bobbrow commented Sep 14, 2021

anb0s commented Sep 14, 2021

bobbrow commented Sep 14, 2021

anb0s commented Sep 14, 2021

bobbrow commented Sep 14, 2021

anb0s commented Sep 14, 2021

anb0s commented Sep 14, 2021

anb0s commented Sep 14, 2021

bobbrow commented Sep 15, 2021

anb0s commented Sep 12, 2021 •

edited

Loading

bobbrow commented Sep 13, 2021 •

edited

Loading

anb0s commented Sep 14, 2021 •

edited

Loading

anb0s commented Sep 14, 2021 •

edited

Loading