Why can't I debug?

Question

When I was about to debug C++ program in VS2005,the program didn\'t stop at the breakpoints.

The VS said\"No symbols are loaded for any call stack frame. The source

Answer 1

A few steps to try:

1. Debug->Step Into (this will ensure you stop right after you start)
2. Debug->Windows->Modules
3. Look for your foo.exe on the list.
4. Check Symbol Status. Does it say it is loaded?
5. If not, go to the path and ensure that: a) there is a file called foo.pdb there b) the timestamp on foo.pdb matches foo.exe (or is really close)

Answer 2

I've experienced this problem (using c# in VS) when trying to debug my unit tests.

You can add the following code that will launch a new instance of the debugger that will allow you yo step through your code like normal:

System.Diagnostics.Debugger.Launch();
System.Diagnostics.Debugger.Break();

Answer 3

Just to add another possibility not yet covered by MainID:

When debugging, I actually started some program that would call into the classes I wanted to debug (it's some sort of add on). The called program is partly written in unmanaged C++. When I checked "Enable unmanaged code debugging" the error would come up (and subsequently the program crashed) because the program did not have any debug information.

Answer 4

Thanks to everybody.

Finally,I found a solution here.

To enable debugging:

1) Goto Project->HelloWorld Properties

2) On the left expand "Configuration Properties"

3) Expand "C/C++"

4) On the left, Select "General"

5) On the right, change "Debug Information Format" to "Program Database For Edit And Continue (/ZI)"

5) On the left, Select "Optimization"

6) On the right, change "Optimization" to "Disabled (/Od)"

7) On the left, expand "Linker"

8) On the left, select "Debugging"

9) On the right, change "Generate Debug Info" to "Yes"

10) Click ok

11) Set your breakpoints

12) Rebuild your application

Also when running your application use Ctrl+F5 to build and run it, this keeps the console window open long enough for you to see your output.

Answer 5

Complete clean and rebuild, making sure .pdb's get created?

Answer 6

It sounds like you're attaching to a process rather than running a conventional debug session? If you are indeed attaching to a process, it is important to ensure that binaries that you are trying to debug were built with the same source code currently open in your IDE.