ARTICLE AD BOX
I recently had an update of vscode (now version: 1.112.0), and suddenly I wasn't able to start the debugger any more on my C++ project.
I have a launch.json with a debugger configuration (which was previously working like a charm), but when pressing F5 it just stays silent.
"name": "(gdb) Launch", "type": "cppdbg", "request": "launch", "program": "${workspaceFolder}/projectXY", "args": [], "stopAtEntry": false, "cwd": "${workspaceFolder}", "environment": [], "externalConsole": false, "MIMode": "gdb", "setupCommands": [ { "description": "Enable pretty-printing for gdb", "text": "-enable-pretty-printing", "ignoreFailures": true } ], "preLaunchTask": "build", "miDebuggerPath": "/usr/bin/gdb"When I press the debugger symbol of cmake, it starts building, but the debugger is somehow not launched:
[main] Building folder: /home/rasmus/Code/C++/projectXY/out/build/projectXY projectXY [build] Starting build [proc] Executing command: /usr/bin/cmake --build /home/rasmus/Code/C++/projectXY/out/build/projectXY --target projectXY -- [build] [100%] Built target projectXY [driver] Build completed: 00:00:00.115 [build] Build finished with exit code 0 [proc] Executing command: /usr/bin/gdb --versionI can run /usr/bin/gdb from the terminal, but the last column confuses me a bit. Why does cmake call /usr/bin/gdb --version? This command doesn't start the debugger.
Please help me, I'm lost without debugger.
