You can also decide which types of errors and warnings you’d like the debugger you automatically break on. Using these breakpoints, you can step into, over, and out of them, as well as pause or continue the executing scope like a normal debugger.Īs you can see above, you can use the call stack in the CMake debugger to see filenames and lines associated with your debugging process. You can set breakpoints based on file names, line numbers, or when CMake errors and warnings are triggered in your CMakeLists.txt file by clicking in the margin to the left of the line numbers like normally or by using the Breakpoint and Exception Settings.

When CMake cache generation on your project fails, a “Debug” link will also be available to start a CMake debugg er session in the Solution Explorer. To initiate a CMake debugging session, you can select “Configure with CMake Debugger” from the context menu when right-clicking on your CMakeLists.txt file in the Solution Explorer or from the “Project” dropdown menu. We are excited to announce that a preview of the CMake debugger is now available to debug your CMake scripts and CMakeLists.txt file for any CMake project in Visual Studio 17.6 Preview 1. We will be contributing this work back upstream (targeting the 3.27 release) so that the developer community can have it and work to improve it together, by adding new features and support f or additional DAP capabilities. The VS CMake team has been working in close collaboration with Kitware on developing a debugger for CMake scripts in the Visual Studio IDE ( s ee this open Kitware issue for more details ).

Cmake visual studio run