pdb-files

问题 A question about pdb file. Is pdb file for debugging in Visual Studio? If so, why do they also exist in my Release folder? It's normal that pdb files are in Debug folder, but why they are also in Release folder. So I have now a Release folder build by Integration team with all the pdb files. Now I can load all the corresponding source (in GIT) so I'm sure that the binaries correspond to the source. Then do I need to build again in order to debug in Visual Studio? If not, what I have to do in

问题 IDE: I use Visual Studio 2015 Update 3 (Language: C#, .NET 4.5). Issue: When I compile a release solution a PDB file is generated. Question: How to disable PDB file creation in Visual Studio 2015? 回答1: In the main menu navigate to Project , and at the bottom Project Name Properties . In the left pane, click on Build , then you should see: Now, click on Advanced button at the bottom-right corner. Finally, you can chose None in Debug info . 来源： https://stackoverflow.com/questions/46784553/how

问题 Does anyone know how to get the GUID from a PDB file? I'm using Microsoft's Debug Interface Access SDK http://msdn.microsoft.com/en-us/library/f0756hat.aspx and getting E_PDB_INVALID_SIG when passing in the GUID i expect when trying to load the PDB. I'd just like to know the GUID of the PDB so I can be certain that it's mismatching and not just a PDB that's perhaps corrupted somehow. Is there a tool that can do this? I've tried dia2dump and dumpbin, but with no joy... Many thanks, thoughton.

问题 i have a Win32 compiler which, for years, has been able to create a DBG debug information file. This has allowed debuggers, and tools like Process Explorer and Process Monitor to have access to symbol information: i recently learned that Visual Studio's debugger no longer accepts DBG files, only undocumented Program Database (PDB) files: Since Microsoft keeps the PDB format secret, i assume they have a tool that will allow me to convert existing debugging information to a PDB (so i don't

问题 I am creating a C# hello world DLL and compiling it with the built-in powershell Add-Type command. When doing so, it creates an unwanted .pdb debug file in the directory with the .dll. How do I suppress creation of this .pdb file when using Add-Type command. I know in Visual studio we can disable that via an option, but cannot seem to find a proper cmd line syntax. Here is the example powershell code. Run from console and it will create the DLL on C:\ along with the .pdb Clear-Host Add-Type

问题 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

问题 What is the size limit on PDB files in VS2k8? I am on a dev workstation with 3GB each of RAM and pagefile on a 32-bit PAE kernel, but the linker kicks out an LNK1201 error shortly after the PDB grows past 1GB. Is MSPDBSRV simply running out of address space? 来源： https://stackoverflow.com/questions/9162001/vs2008-pdb-file-size-limit-redux-lnk1201-too

问题 After loading a DLL library using LoadLibrary("file.dll") visual studio also opens and locks file.pdb . The problem is - the file.pdb is kept locked even after calling FreeLibrary(...) . It is necessary to recompile file.dll and reload it once again ( externally, outside of MSVS , using CL.exe ), but the compilation fails because file.pdb is still locked. How to make Visual Studio 2015 release the file lock? 回答1: Coincidentally I've stumbled upon a solution to this: Go to Tools -> Options

问题 I have a weird problem with PDB files in a VS 2013 C# project. Basically what is happening is that the PDB files are not getting rebuilt when the project is getting rebuilt. This is causing the project to always think it needs to get rebuilt. I've tried cleaning the solution, but if anything changes in the project it gets put back into the same state again. I created a simple class library project and the behavior was the same. As a sanity check, I created the same class library on another PC

问题 Is it possible for the debugger (or the CLR exception handler) to show the line where the exception happened in Release mode using the pdb? The code, in release mode, is optimized and do not always follow the order and logic of the "original" code. It's also surprising that the debugger can navigate through my code step by step, even in Release mode. The optimization should make the navigation very inconfortable. Could you please clarify those two points for me? 回答1: I'm not as familiar with