question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

message(DEBUG "...") doesn't display in VSCode output?

See original GitHub issue

Brief Issue Summary

While working on my projects I added some message(DEBUG "...") statements. I also set "cmake.loggingLevel": "debug".

Expected:

What I expected to see was the message statements from DEBUG and above.

Apparent Behavior:

What I do see is that there is some extra info the the VSCode Output [driver] messages etc. But none of the message(DEBUG "...") statements.

If I use message(STATUS "...") then I do see the messages.

Have I misinterpreted the cmake.loggingLevel settings? Is that not controlling the log level of CMake when it runs?

CMake Tools Log

[driver] Start configure 
[driver] Runnnig pre-configure checks and steps
[driver] Run _refreshExpansions
[cms-driver] Run doRefreshExpansions
[driver] Run _refreshExpansions cb
[cmake] Configuring done
[cmake] CMake Deprecation Warning:
[cmake]   The 'cmake-server(7)' is deprecated.  Please port clients to use the
[cmake]   'cmake-file-api(7)' instead.
[cmake] 
[cmake] 
[cmake] Generating done
[cache] Reading CMake cache file c:/Users/Thomas/SourceTree/traceup/cext/build/Release/CMakeCache.txt
[cache] Parsing CMake cache string
[extension] [1947] cmake.configure finished (returned 0)
[kit] OK running C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvarsall.bat amd64, env vars: undefined

Platform and Versions

  • Operating System: Windows 10
  • CMake Version: 3.15.4
  • VSCode Version: 1.40.0
  • CMake Tools Extension Version: 1.2.1
  • Compiler/Toolchain: Visual C++ 2019

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:7 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
thomthomcommented, Mar 23, 2020

Ah! After updating to CMake 3.16 the above worked as expected. Must be 3.15 being bugged.

0reactions
bobbrowcommented, Mar 28, 2020

That’s great! I’ll close the issue.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Debugging in Visual Studio Code
To run or debug a simple app in VS Code, select Run and Debug on the Debug start view or press F5 and...
Read more >
GDB in Visual Studio Code doesn't show printf() output to ...
When debugging a C project in VSCode with GDB, the output to stdout (through printf()) does not appear on the Debug Console.
Read more >
NT
Debug console not showing in visual studio code. After completion the below message shows in the command window; VS Code left Navigation --...
Read more >
Output Window - Visual Studio
Visual Studio Code. The Output window displays status messages for various features in the integrated development environment (IDE).
Read more >
Using console.log() debugging in Visual Studio Code
Visual Studio Code now opens a browser window for you and you can see the console.log message from the demo code in the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found