VS code is ignoring the breakpoint in c++ debugging

Question

I am debugging a c++ code in VS Code but it doesn't stop on breakpoint and visualize the variables, watch and call stack, which it was supposed to do. Instead of this, it prints this in debug console:

Breakpoint 1, 0x000000000040074a in main ()
[Inferior 1 (process 9445) exited normally]
The program '/home/hashir/x/a.out' has exited with code 0 (0x00000000)

here is launch.json file:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "(gdb) Launch",
            "type": "cppdbg",
            "request": "launch",
            "program": "/home/hashir/x/a.out",
            "args": [],
            "stopAtEntry": false,
            "cwd": "/home/hashir/x/",
            "environment": [],
            "externalConsole": true,
            "MIMode": "gdb",
            "setupCommands": [
                {
                    "description": "Enable pretty-printing for gdb",
                    "text": "-enable-pretty-printing",
                    "ignoreFailures": true
                }
            ]
        }
    ]
}

`"stopAtEntry": false` should it be `"stopAtEntry": true`? – ks1322 Jan 15 '18 at 18:00 — ks1322, Jan 15 '18 at 18:00

score 35 · Accepted Answer · edited Dec 18 '22 at 02:57

35

Compile the program using the -g tag along with g++/clang++.

edited Dec 18 '22 at 02:57

Rohan Bari

7,482
3
14
34

answered Jan 15 '18 at 18:58

Hashir Sarwar

1,115
2
14
28

Thank you, I was facing the same issue. Your answer helped me. – KK2491 Dec 31 '20 at 02:53
Any extra clarification on where to enter this tag specifically? Thanks. – andreyb Mar 16 '21 at 15:14
@andreyb add that flag when you are compiling, as in running the g++ file.cpp command. – Oreo Jun 18 '21 at 20:44

score 3 · Answer 2 · answered May 08 '21 at 15:36

3

This problem literally ruined my day. It turned out that all I had to do is just Terminal > Run Build Task or Ctrl+Shift + B and then start debugging.

answered May 08 '21 at 15:36

temmmy

31
3

wtf! this solved my problem too! eventhough there is a preLaunchTask tag in launch.json. Thanks! – CppChase Nov 30 '21 at 12:23

score 1 · Answer 3 · answered Feb 15 '20 at 22:00

I've figured out that if your source-code file name contains white spaces, like "Binary Search.cpp", VSCode will ignore the breakpoints regardless of "stop at entry" configuration. Removing the white spaces from my source files' names worked, although their paths contain white spaces. For example "C++ Exercises/BinarySearch.cpp" seems to be valid.

In this issue opened on GitHub, it is suggested that non-ascii characters might cause such problems.

score 0 · Answer 4 · answered Apr 13 '22 at 17:55

The default launch.json file has this line:
"program": "${workspaceFolder}/a.out",
But this will run a.out to start debugging, and if you configured tasks.json file with only one cpp file, it will have lines like:

                "-o",
                "${fileDirname}/${fileBasenameNoExtension}"

this will create an executable with the same name with your current file.
Either change the tasks.json to create an a.out file or change launch.json file with the no extension name of your current file.

launch.json:

"program": "${workspaceFolder}/<stripped current file name>",

OR
tasks.json:

                "-o",
                "${fileDirname}/a.out"

score 0 · Answer 5 · answered Jul 12 '22 at 00:09

0

It seem something wrong with environment vars, try open vscode from "developer command prompt for VScode", then on prompt, type: code

answered Jul 12 '22 at 00:09

Bigumangaba

41
5

VS code is ignoring the breakpoint in c++ debugging

5 Answers5

Linked

Related