符号文件未加载用于在 Visual Studio 2012 中调试自定义项目

Question

I have a large solution in Visual Studio 2012 which consists of executables and class library projects. When debugging the application the breakpoints in one particular class library project are not being hit.

I looked at the Debug> Windows> Modules window to check the status of the symbols for that project and it says "Cannot find or open the PDB file" .
It also says "No" under the "User Code" column.
I notice that there are a few other of the custom projects in the solution that are showing "No" in that column and their symbols are also failing to load. Anything with a "Yes" under "User code" seems to have had it's pdb loaded no problem. But I'm not sure if this is relevant.

I have used dumpbin /headers on the dll and the path for the pdb file is present and correct.

The module is definitely not in the exclude list for the symbol loading.

I have also tried right clicking on the entry in the modules window, selecting "Load symbols" and navigating to the path given in the dll header. When I select the pdb it says "A matching symbol file was not found in this folder" .

I get this after I have deleted these folders and files, cleaned the solution, closed it and rebuilt the whole thing. The pdb was definitely built at the same time as the dll in question.

So clearly the problem is the "cannot open the pdb" portion of the error message.

I have tried this on 2 computers and both are exhibiting the same behaviour.

Can anyone offer any suggestions on where to go from here, and perhaps why on earth the built pdb corresponding to the dll won't load for it?

Answer 1

I tried a few tools to check if the pdb and the dll actually matched, and using chkmatch I could see that the GUIDs in the dll being run and the pdb in the obj folder didn't match.

So it turns out that although the dll and pdb in the project's obj folder are a match, the dll that was actually getting copied to the application's destination folder by a post-build event was the old dll from the previous build.

The post-build event was running before that particular project had built, or at least finished building, and was copying in the existing dll from the bin which was subsequently overwritten by the continuing build.

I have resolved the problem by editing the project dependencies for the solution and ensuring that the project with the post-build event is dependent on the project that wasn't loading, and now the pdb loads during debug.

Answer 2

我只是从启动项目文件夹中删除了 bin 和 obj 文件夹并重建了解决方案。

Answer 3

对我来说，我刚刚从 IIS 中删除了该项目并再次创建它，它工作正常

Answer 4

For me it helped to use chkmatch tool and then just close and open visual studio, make clean and rebuild. Now my pdb gets also loaded. You can make sure it does, as Nanhydrin pointed out, from Debug -> Windows -> Modules - this view is only accessible during debugging.

Answer 5

I found that the project I was receiving the message about, was being optimized when built.

I went into the projects properties, Compile Tab, Advanced Compile Options... and unchecked the Enable Optimizations checkbox

Answer 6

In my case older version of referenced dll was in my GAC. Cleared it out, and it worked.

Answer 7

In my case there was a check mark on Enable Just My Code in Tools>>Options>>Debugging>>General .

I unchecked it and it worked.

Example Image

Answer 8

提醒：将项目放入“调试”配置中...对于像我这样忘记并感到愚蠢的人。

Answer 9

Deleted the project from solution and added it again to the solution worked for me. :)

Answer 10

Bit late to the party here - just in case this is helpful.

We have a couple of separate websites (in different solutions in Visual Studio). On initial load of one of the sites, we were making a call to the other site which would return an image.

Both of these sites referenced a common DLL, but while working on one site, had not realised that the other site had been left in a 'Release' build - after the site loaded, the offending DLL was rebuilt, but without symbols.

Kudos to Nanhydrin for both mentioning the modules debug window (very helpful) and for putting me on the right track with the post build event.

Answer 11

Answer from another thread that worked for me: https://stackoverflow.com/a/28476665/5969306
- In Visual Studio: Project Properties -> Build -> Advanced button -> Debug info drop-down and make sure the value is not “none”.

Answer 12

I just had this issue and thought I would put my fix here, as it my help others (maybe even myself again?!) in the future...

Make sure that when you are attaching to the process on the remote server, that the "Attach to" is set to

Automatically determine the type of code to debug

To do this, When the server qualifier has been provided and a list of processes is visible, click the "Select" button next to the "Attach to" input.

Then, select "Automatically determine the type of code to debug" and OK out of the screen, then attach.

This fixed the issue for me, at least.

Answer 13

I had a line like this in my debug window:

Symbols for the module 'MyModule.dll' were not loaded.

I removed the 'Optimize code' option in Project properties -> Build. And the error disappeared.

Answer 14

This issue may be due to wrong reference of dlls used in project.

Delete obj and bin folders in current project and build project again.

Answer 15

Check for permission to ASP.NET Temporary folder:

"c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files"

User of application pool has to have the rights to subfolder with ASP.NET files, something like:

root\60039743\c28e12ee

Answer 16

1. Check options from this answer: https://stackoverflow.com/a/38377530/6911991
2. Click Advanced and check that Debugging Information is set to FULL
   
3. Check Run Configuration in all projects in the solution

Answer 17

I had this issue , tried all the other solutions (it took 2 days !! I'm crying... !TWO DAYS!) But finally I realized that my file was registered in GAC, I removed it and the problem was resolved.

At the command prompt, type the following command:

gacutil –u <assembly name>

How to: Remove an Assembly from the Global Assembly Cache

Answer 18

请检查您的 dll 的依赖关系，如果您添加到解决方案中，这可能会导致加载符号失败。

Answer 19

I resolved this issue by disabling 'Use Managed Compatibility Mode' in the Debug->Options menu: