How to setup C++ with debugger on mac in visual studio code - c++

Question

I am trying to setup visual studio code to build/run and debug c++ files using g++ compiler on macOS. However when I build or debug the code, I can see that output file is created and i can run it as well however i am not able to debug it in vscode, for debugging gives weird behaviour.
So far I have been able to write tasks which builds the .cpp file and and executes it. The output comes into the terminal of vscode. However when I try with debug a new Terminal opens and no breakpoint is hit.
Here is the tasks.json
{
"version": "2.0.0",
"tasks": [
{
"label": "Build with g++",
"type": "shell",
"command": "g++",
"args": [
"-Wall",
"-Wextra",
"-Wpedantic",
"-std=c++11",
"${file}",
"-o",
"${fileDirname}/${fileBasenameNoExtension}"
],
"group": {
"kind": "build",
"isDefault": true
}
},
{
"label": "run",
"type": "shell",
"command": "cd ${fileDirname}/ && ./${fileBasenameNoExtension}",
"dependsOn": ["Build with g++"]
}
]
}
and here is my launch.json
{
"version": "0.2.0",
"configurations": [
{
"name": "(lldb) Launch",
"type": "cppdbg",
"request": "launch",
"program": "${fileDirname}/${fileBasenameNoExtension}",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"showDisplayString": false,
"environment": [],
"externalConsole": true,
"internalConsoleOptions": "openOnSessionStart",
"MIMode": "lldb",
"logging": {
"moduleLoad": false,
"programOutput": true,
"trace": false
},
"preLaunchTask": "Build with g++",
"osx": {
"MIMode": "lldb"
}
}
]
}
I expect that when i hit debug or press f5 the terminal in the vscode should run and I am able to debug the program.

Answer 1

As #alan-birtles pointed out adding -g would be the solution.
Also I found out here that there is no way to use integrated terminal of vscode for c++ as lldb doesn't support it.
Here are the final configuration.
launch.json
{
"version": "0.2.0",
"configurations": [
{
"name": "(lldb) Launch",
"type": "cppdbg",
"request": "launch",
"program": "${fileDirname}/${fileBasenameNoExtension}",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"showDisplayString": false,
"environment": [],
"externalConsole": true,
"internalConsoleOptions": "openOnSessionStart",
"MIMode": "lldb",
"logging": {
"moduleLoad": false,
"programOutput": true,
"trace": false
},
"preLaunchTask": "Build with g++",
"osx": {
"MIMode": "lldb"
}
}
]
}
task.json
{
"version": "2.0.0",
"tasks": [
{
"label": "Build with g++",
"type": "shell",
"command": "g++",
"args": [
"-g",
"-Wall",
"-Wextra",
"-Wpedantic",
"-std=c++11",
"${file}",
"-o",
"${fileDirname}/${fileBasenameNoExtension}"
],
"group": {
"kind": "build",
"isDefault": true
}
},
{
"label": "run",
"type": "shell",
"command": "cd ${fileDirname}/ && ./${fileBasenameNoExtension}",
"dependsOn": ["Build with g++"]
}
]
}

Answer 2

Because your VSCode Debugger Extension has bugger.
Successfully Setup C++ Debug with VSCode on mac:
I use clang/gcc as compiler, Code-Runner(VSCode Extension) as runner, C/C++ Clang Command Adopter(VSCode Extension) as to provide static detection, CodeLLDB(VSCode Extension) to debug C++.
Do Not Download Microsoft C/C++ (Identifier: ms-vscode.cpptools, for C/C++
IntelliSense, debugging, and code browsing. Microsoft Officially produced Extension), Because This CPPtools and that CodeLLDb conflict.
To avoid any issues, please do not download any VSCode Extensions yet.
Here is my configuration about debug C++ with VSCode on mac:
VSCode v1.63.2;
Code Runner v0.11.6 (Author: Jun Han）
C/C++ Clang Command Adapter v0.2.4 (Author: Yasuaki MITANI）
CodeLLDB v1.4.5 (Author: Vadim Chugunov)
Clang v9.0.0 gcc v4.2.1 Intel CPU macOS 10.12
Details of successful configuration refer to here：
Debug C++11 manually with VSCode(mac)