-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
disable some debug console messages #5861
Comments
You can disable these outputs by adding a |
Thanks! No module loaded logs anymore. {
"name": "(Windows) Launch",
"type": "cppvsdbg",
"request": "launch",
"program": "${command:cmake.launchTargetPath}",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [],
"externalConsole": false,
"logging": {
"moduleLoad": false,
"threadExit": false,
"processExit": false
}
} Gives: -------------------------------------------------------------------
You may only use the C/C++ Extension for Visual Studio Code with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications.
-------------------------------------------------------------------
The thread 23004 has exited with code 0 (0x0).
... program output
The thread 12584 has exited with code 0 (0x0).
... program output
The thread 8184 has exited with code 0 (0x0).
... program output
The program '[18604] json_message.exe' has exited with code 0 (0x0). |
The thread and process exit messages logging is available in v1.1.0. This should be in the vsdbg version 16.4.202272. You can find this at |
This works really well but there's still this message at the top:
Is there a setting I can turn on to disable printing this? |
I am able to hide moduleLoad message and others but I am still seeing the first 3 lines. Is there a way to hide it? |
Type: Debugger
Describe the bug
How do disable messages with the yellow color such as the one about
pdb
and 'thread'I find these messages very annoying and mixed with my console output sometimes.
To Reproduce
compile and run in vs code.
The text was updated successfully, but these errors were encountered: