symbol-server

I am having Windows 7 x64 SP1. I have downloaded symbols from: http://msdn.microsoft.com/en-us/windows/hardware/gg463028 I have downloaded and installed x64 RTM and x64 SP1 symbols for Windows 7 x64 SP1. Installed on T:\Symbols folder. But When I debug a 64-bit native C++ application, the symbols would not load at all. For ntdll.dll , for instance, the PDBs are located in: T:\Symbols\ntdll.pdb\6192BFDB9F04442995FFCB0BE95172E12 T:\Symbols\ntdll.pdb\CFF40300FD804691B73E12CF2A150EE02 But Visual Studio (2008/2010) will not load symbols. While debugging, from Modules View, I select ntdll.dll and

I created a powershell script that gets all the pdb files from the drop location after the build is set to release and copies them to a folder that is shared on the network. I also created a sample application and I added the nuget packages that contain the assemblies that I need (without the pdb files). I found some references on the net, but I was unable to debug my assemblies using the pdb files. I am using a VPN connection to connect to the shared folder that contains the pdb files and Visual Studio 2010. What are the exact steps that I need to make in order to use the pdb files that are

I read through this article: Setting up a Symbol Server , which goes into details on how to set up a shared symbol server for my team. The thing I'm wondering about is adding my own symbols into the store. My question is this: What exactly is it that I gain from this? Let's assume that I have the following build process: I commit changes into my Subversion repository A TeamCity CI tool picks up those changes and does a build + unit testing The binaries are committed to a different Subversion repository (for referencing by applications I make) If I add to the third point above, the ability to

I am trying to figure out what hashing algorithm is used for the Microsoft Symbol Local Cache directory. For example, the local cache can be something like the following L:\Symbols \browseui.dll \44FBC679fe000 browsue.dll \browseui.pdb \44F402F62 browseui.pdb \explorer.exe \3EBF1F14f7000 explorer.exe \explorer.pdb \3EBF1F141 explorer.pdb \msvcr71.pdb \60D915C6AB6A4F3586E9096E2F8856482 msvcr71.pdb There seems to be some sort of correspondence between a file and its debug database. Other than that, I can’t figure out how the names of these (presumably) hexadecimal string folders are being

Our nightly build process was broken for a long time, such that it generated PDB files that were a few hours different in age than the corresponding image files. I have since fixed the problem. However, I would like to start using a symbol server, but cannot due to having to use these age-mismatched pdb files. I work around this issue by using the .symopt +0x40 method in windbg. That means I have to organize all my pdb files by hand, and after years upon years of releases, that adds up. I am looking for a way to modify the mechanism that windbg uses to mark a pdb's age, and force it to match

I have put a library that my team uses into a nuget package that is deployed from TeamCity into a network folder. I cannot debug into this code though! SymbolSource is one solution I have read about but I would much rather find some way to have access to the .pdb/source files directly from Teamcity. Does anyone know how to do this? Edit. When I check 'Include Symbols and Source' in the Nuget Pack build step TeamCity creates a .Symbol.nupkg in addition to the .nupkg file in the network folder. The .Symbol.nupkg contains the src and the .pdb file. Edit. I unchecked 'Include Symbols and Source'