Breakpoints cannot be set and disabled

Question

If I add a breakpoint in the VC ++ 6.0 project and then start debugging, it will display this error message:

One or more breakpoints cannot be set and disabled. Execution will be stopped at the beginning of the program.

and displays the disassembly window. What is this problem?

How to add a breakpoint and start debugging?

Answer 1

Check:

• http://www.tek-tips.com/viewthread.cfm?qid=326950]
• http://www.codeguru.com/forum/archive/index.php/t-118951.html

A plus:

KB957912 - Update for Visual Studio 2008 Service Pack 1 Debugging and Breakpoints http://code.msdn.microsoft.com/KB957912/Release/ProjectReleases.aspx?ReleaseId=1796

Answer 2

This problem occurs mainly when you set breakpoints in the source files other than the ones you start debugging with.

Suppose you started debugging the MainModule.dsw workspace, and from this open visual studio editor you inserted breakpoints in other cpp files, and then at the very beginning of debugging you get this error.

Instead of the build code, your editor should show the winmain or dllmain method if you set the source code path to the vc folder of the Visual Studio installaiton installation. Then you can understand what the basic logic of the error message is.

Answer 3

I also had such a problem, but the code worked fine, and I even compared all the files with another instance that worked. The problem was a dash with leading and trailing spaces in the path. As soon as I deleted the trailing space (for example, "-dir" became "-dir"), then it worked fine. Although you can generally avoid dashes, if possible. Hope this helps someone else.

Answer 4

The first two things to check:

• Have you compiled your C ++ code with the correct settings for debugging information?
• Did you also tell the linker to generate debug information?

Both of them are usually disabled when you create the binary in the release configuration. IME, the most common reason for the above error is because someone forgot to tell the linker about sending debugging information ...

I also saw this problem when a binary file with corrupted debugging information was associated with an executable and displaying unacceptable debugging information.

Answer 5

Most likely you have "Win32 Release" as the active configuration. Install it in "Win32 Debug", after which you will receive the necessary information for debugging.