Visual Studio is tricky every time a "puzzling question" comes up. This is a problem:
New Windows Console window program (c + +), compile link run no problem. But want to try a single step, so in the program somewhere to hit a breakpoint, and then run the program, the program can stop at the breakpoint, but continue to do not go down, will jump out of the program directly executed. Therefore, from the performance point of view, the program can not be single-step debugging. And does not seem to be completely single-step execution, just as long as the function of the call, just jump out, go to the assembly mode of single-step debugging, one step of the instructions can be single step, a call STD function, jump out. Initially suspected C + + runtime problems, but do not know how to solve, online check why can't adjust the standard library, did not find the answer. Before it was possible, why did it suddenly die? I just want to know what I've done these days.
I think that can have an impact on the cppdepend, so disable the plugin. It's still not working. No way, had to put the VS unload the reload, the result is still not (from the back of the results, should be uninstalled dirty, some settings or retained). There's really no way. Finally, in the debugging process, if you add a breakpoint, a dialog box pops up saying: "Breakpoint failed to bind"
According to this information, and then go online to see, find csdn on a net article, according to the above tips, finally found the problem:
Tools-Option-〉 Debug-〉 Edit and Continue-〉 enable native editing and continue with the check box
The problem has been in the pit for several days. Leave a few pens handy for others.
One Visual Studio cannot step through (function call) issues