Currently, no breakpoint hits. No symbols have been loaded for this document (reprinted)

Source: Internet
Author: User

In vs2010, I changed the red part below, and the following is the reprinted content:

I believe many people have encountered this problem during web programming, that is, a prompt is given when the breakpoint is set, and cannot be selected later. I also encountered this problem today, and it took me a whole day. The setting is Debug. I have not found the "C/C ++-> General-> debugging information format". It is estimated that the setting is in C ++, I use C #." Cancel the check box that "requires the source file to exactly match the original version". "I tried it too, but the debug setting in webconfig is also true. After one day, I found that there is a webconfig in the folder where the text to be debugged is located. The debug here is false. After I searched the internet, I realized that the webconfig on the outermost side was the total. Webconfig can also be set inside the folder. This webconfig inherits the information of the total webconfig and also has its own attributes of the subfolders. Therefore, my total webconfig although debug is true. But because the program in the folder should refer to the internal webconfig. Therefore, you still cannot set breakpoints for debugging. It's really careless.

 

 

Debugging is not broken. Check the options of. I tried my best to find the methods I have used:

1. Delete the debug of the referenced Project

2. Check "generate" of all projects in the Configuration Manager and select "debug" for "configuration". Do not release

3. "Active solution configuration" in the Configuration Manager and create a solution

4. Set the reference directory to a directory to prevent the latest version from being referenced (the source code does not match the dll version)

5. Remove the check box for tools, options, debugging, and general requirements for "exact match between source file and original version"

Five methods have been used. Still useless.

Finally, I accidentally thought that there were two reasons for this problem:

1. The DLL to be debugged is not in the process space of the debugging process and cannot be called

2. The DLL used in the source code is not the same as the version of the source code for debugging. Naturally, the source code cannot be debugged.

The first line is out. It must be the second one. I finally remembered it. I have referenced three or four project files. Some project files do not reference the existing project on the "project", but directly reference a DLL that has been in use all the time. Delete the reference and reference it to an existing project.

 

The breakpoint set in http://johnsmithblog.blogbus.com/logs/15017286.html vs2005 is invalid: "the breakpoint is not hit currently and no symbols are loaded for this document ". After a while, the main problem was that debugging information was not generated. The solution is as follows:

(1) Project-> property-> Configuration property-> C/C ++-> General-> debugging information format, which cannot be disabled here ".

(2) Project-> property-> Configuration property-> linker-> debugging-> Generate debugging information. Here it is set to "yes ".

(3) 2005 the default MFC program is linked using the dynamic MFC Library (use MFC in a shared DLL), while the dynamic MFC library uses the multi-threaded DLL (/MD) XP is more rigorous in monitoring PE file formats. this will cause some executable files that use multi-threaded DLL to make an error when calling the compilation switch project-> property-> Configuration properties-> C/C ++-> code generation-> Runtime Library modified to multi-threaded (/mt)

I hope this article will help people who encounter the same problems as me :)

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.