Debugging symbols not working + hundreds of LNK4099 warnings ("linking object as if no debug info")

[Tristan Schmelcher]

Hi all. I have built Chromium on Win XP with Visual Studio 2005 and it runs fine, but I'm having an issue with the debugging symbols. If I attach VS to Chromium and set a breakpoint somewhere in the source, it displays a warning symbol and says in the hover text that:

"The breakpoint will not currently be hit. No symbols have been loaded for this document."

However, the "Modules" tab shows that all symbols have loaded.

I suspect this may be related to the fact that I am seeing hundreds of LNK4099 warnings when linking chrome.dll. e.g.:

webkit.lib(WebDocument.obj) : warning LNK4099: PDB 'vc80.pdb' was not found with '.\debug\lib\webkit.lib' or at 'C:\src\chromiumtrunk\src\chrome\Debug\vc80.pdb'; linking object as if no debug info

There are many many pages of those errors for different .lib and .obj files.

Has anyone seen this issue before?

[Finnur Thorarinsson]

I remember seeing similar problems in the past on occasion and a rebuild of chrome has fixed them for me. 

Not entirely sure this is the same problem you are seeing but I thought I should mention it, in case you hadn't tried it. 

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Steven Bennetts]

I have seen this before with very large projects in VS 2005. I believe it was a corruption of either the .pdb file or one of the large intermediate files produced in the output directory. Deleting these may do the trick, otherwise a rebuild should do the job, although I recall something about rebuild not actually cleaning out everything, so you may need to try an explicit clean or deleting the output directory. If you do any file deletions I recommend exiting VS first.

[Tristan Schmelcher]

Thanks guys, that helped. I closed VS, deleted the chrome/Debug directory, then reopened the solution and rebuilt it and I no longer had those linker warnings.

I did however hit two other issues afterwards, but I was able to resolve them. The first was that I got tons of C2471 errors while building webkit.lib, e.g.:

c:\src\chromiumtrunk\src\third_party\WebKit\JavaScriptCore\wtf/Platform.h : error C2471: cannot update program database 'c:\src\chromiumtrunk\src\chrome\debug\obj\webkit\webkit\vc80.pdb'

But simply deleting chrome\Debug\obj\webkit and then building again fixed that.

The second issue was that VS refused to load the symbols for chrome.dll from chrome_dll.pdb, insisting that "The symbol file chrome_dll.pdb does not match the module." But based on mungflesh's comment at http://social.msdn.microsoft.com/forums/en-US/vsdebug/thread/86125819-426b-4794-948d-d2252f46aedf/ I just restarted VS and that fixed the problem (probably it implements a half-baked GUID cache or something). I now can finally debug Chromium.