[SOLVED!] How to fix Unverified Breakpoints

Hi @DanM,


I didn’t download anything extra, just the MSBuild tools.

Thanks,
Enrico

You didn’t install it. You need to tick the box for C++ Build Tools.

Hi @DanM,

Should I tick/untick any boxes? Or would you say the optional 4 plus the build tools are good enough?

Thanks,
Enrico

That should be enough

Hi @DanM,


Thank you so much! I can finally compile again!
I have no idea how this error came about because I never remember deleting anything. Anyways, the important thing is that I can now compile and continue with the lectures.

You probably wish this was over … but I still have two more questions: (sorry …)

  1. Where can I find the article on #include in Udemy. What section is it under and what name is displayed in Udemy?
  2. My terminal continues to say this:
    debug36
    What does this mean? Is it something I have to fix that will hurt me down the line or is it fine?

Again, thank you so so much for helping me through this!

Thanks, :blush:
Enrico

  1. It’s under the TripleX section, I believe I called it “A note to Windows Users”
  2. That’s the output. The output of the compilation was those files.

Hi @DanM,

Thank you! Everything is working now!
Debugging is still a problem, but I’ll wait to affront that issue again in the next project.

Thanks again for helping me because I certainly couldn’t have done it without you!

Thank you,
Enrico

Hi @DanM,

Actually I was too curious to see what would happen when I debug…
So I went back to the original project (which is now working by the way!) and pressed F5. Debugging seems to be working correctly after I changed to "externalConsole": to true.
What doesn’t seem to work is building. When I press “Ctrl+Shift+B” I get this in the console:


Is this occurring because I changed "externalConsole": to true? How can I fix it (that way I can return to my original project…)?

Thanks! :+1:
Enrico

What’s the problem with that output?

Hi @DanM,

I have two questions.

  1. When I booted up VS Code today directly from the desktop and tried compile it tells me that:
'cl.exe' is not recognized as an internal or external command,
operable program or batch file.

However, when I open Developer Command Prompt, type cl, and then type code to open VS Code, compiling works without a problem. I’m just wondering: from now on, do I have to go through dev prompt to open VS Code?

  1. I thought the below screenshot had a problem because then it doesn’t let me run my game. So, I’m just wondering after pressing “Ctrl+Shift+B” and after the terminal tells me this:
    fix1
    How can I then play my game?

Thanks,
Enrico

  1. Yes
  2. How are you trying to play it?

Hello @DanM,

I’m trying to play the game through the terminal like I used to be able to when typing cl main.cpp FBullCowGame.cpp and then typing main FBullCowGame to actually make the game run in the terminal where I can input words.
Here is a screenshot of what I used to be able to do:

Thanks,
Enrico

Refer back to this post [HELP] How to fix Unverified Breakpoints

And look at the output of compilation.

Hi @DanM,

I see. So I don’t have to type all of that stuff to get the program to compile, but I don’t understand what you mean by the “output of compilation.”
And I still don’t see how this brings me closer to being able to play the game.

Sorry for my ignorance again, :woozy_face:
Enrico

The screenshot you posted is you compiling and the output of which. Specifically though I’m referring to this line

/out:BCGame.exe

Hi @DanM,

Which screenshot are you referring to? This one?
What does that line have to do with this? Not that I’m doubting you, just that I don’t understand.

Thanks,
Enrico

That doesn’t have that line in it so no.
The one you just posted here

My point is that the program is not called either “main.exe” or “FBullCowGame.exe”

Hi @DanM,

I don’t think the link is working becuase each time I press it I get directed to this, Post #11 (which is your post). Are you talking about the screenshot in Post #49? If not, please give the post number instead of a link.

Ok, so your saying that the terminal should say something like

/out:main.exe

instead of

/out:BCGame.exe

How can I fix this? I’m using your launch.json and task.json files by the way.

Thanks,
Enrico

P.S. Just so you don’t have to scroll up and down every time to see the .json files here they are:
launch.json

{
    // 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": "Debug",
            "type": "cppvsdbg",
            "request": "launch",
            "program": "build/BCGame.exe",
            "args": [],
            "stopAtEntry": false,
            "cwd": "${workspaceFolder}",
            "environment": [],
            "externalConsole": true,
            "preLaunchTask": "Build"
        }
    ]
}

tasks.json

{
    "version": "2.0.0",
    "tasks": [
        {
            "type": "shell",
            "label": "Build",
            "command": "cl.exe",
            "args": [
                "/Zi",
                "/EHsc",
                "/Fe:",
                "BCGame.exe",
                "${workspaceFolder}\\main.cpp",
                "${workspaceFolder}\\FBullCowGame.cpp"
            ],
            "options": {
                "cwd": "${workspaceFolder}/build"
            },
            "group": {
                "kind": "build",
                "isDefault": true
            },
            "problemMatcher": [
                "$gcc"
            ]
        }
    ]
}

No. I’m saying the program you created is called “BCGame.exe” so “main.exe” or “FBullCowGame.exe” don’t exist. And if you refer back to that post I cited earlier in which I say how you run a program, you should understand what you’re trying to do by typing what you’re typing is incorrect.

BCGame

From the build directory is what you need to type because that’s the name of the program which is specified here

"/Fe:",
"BCGame.exe",

Hi @DanM,

Ok. Now I understand. I can’t run the program by typing cl main.cpp FBullCowGame.cpp and main anymore because those .exe files don’t exist.
Instead, I should only type BCGame.exe, right? The only problem is that the terminal closes when I try to type anything (or is that what’s supposed to happen)?

Thanks

Privacy & Terms