pdb-files

问题 I have a solution containing several projects that have migrated from VS 2003, 2005, 2008. When compiling all the projects for the RELEASE configuration, VS 2008 creates PDB files for some projects, but not others. Why? In the Build tab of the Properties page for each project, I can see they all have "Define DEBUG constant" unchecked and "Optimize code" checked. When I inspect the CSPROJ for each project, I do not notice any differences that look like they would change this behavior. What

问题 I have .pdb file, downloaded from MS symbols server. I need to fetch list of symbols (functions, arguments, anything it has). There is a tool on CodeProject, but it only reports modules. There is DbgHelp API, but it only could be attcahed to running process. How can I read .pdb file offline? 回答1: Good News for anyone still looking, The information you seek is now open source! https://github.com/Microsoft/microsoft-pdb Some real interesting stuff there. Like this pdbdump.cpp file, with its

问题 I want my application to be distributable as a single .exe file but I want to be able to get nice error reports with source code line numbers (the application simply sends email with exception.ToString() and some additional information when unhandled exception occurs). Is there any way to embed .pdb into assembly? 回答1: Use MiniDumps instead of "exception.ToString()". It will give you a lot more information and does not need the .pdb to be distributed with the .exe. Useful Link: Post-Mortem

问题 I want my application to be distributable as a single .exe file but I want to be able to get nice error reports with source code line numbers (the application simply sends email with exception.ToString() and some additional information when unhandled exception occurs). Is there any way to embed .pdb into assembly? 回答1: Use MiniDumps instead of "exception.ToString()". It will give you a lot more information and does not need the .pdb to be distributed with the .exe. Useful Link: Post-Mortem

问题 How can you read the source paths used to compile a pdb in .NET (C#) environment? 回答1: The PDB format is NOT documented - but there is an API from MS called DIA which provides several methods to deal PDB. It is COM-based... for details see MSDN. PDB files usually contain filenames and linenumbers BUT I am not sure that they always contains full path to the source. Some interesting information on PDBs can be found here. IF you want some .NET source code dealing with .PDBs see Mono.Cecil and

问题 Is is wise to redistribute the pdb files along with a commercial application? Occasionally, I'm using the stack trace to get a more detailed error reporting logs from the deployed applications; can this functionality be achieved without relying to those files? Also, how much hints of the original source code does these files contain? Would it be easier to reverse-engineer my application using it? 回答1: It basically adds information for: All non-public types, interfaces, structures, classes

问题 We are currently using a single command line tool to build our product on both Windows and Linux. Si far its works nicely, allowing us to build out of source and with finer dependencies than what any of our previous build system allowed. This buys us great incremental and parallel build capabilities. To describe shortly the build process, we get the usual: .cpp -- cl.exe --> .obj and .pdb multiple .obj and .pdb -- cl.exe --> single .dll .lib .pdb multiple .obj and .pdb -- cl.exe --> single

问题 I want to deploy the release version of my application done in C#. When I build using the Release config, I still can see that .pdb files are produced, meaning that my application can be still debugged. This also means that some debug information is present somewhere in my code, slowing it down a little bit. If this is true, how can I completely suppress any debug information produced in the binaries? Do you also know the reason of for having release .pdb ? The Release configuration has the

问题 In VS2012, I'm statically linking with a precompiled .lib, and need to also use that lib's .pdb file for debugging. How can I tell the linker that it should use that external pdb file? 回答1: If you created the static lib with /ZI or /Zi (see project settings for C/C++ -> General -> Debug Information Format), then the $(IntDir)vc$(PlatformToolsetVersion).pdb file is created. The path is defined by /Fd. A linker that uses the static library usually also refers to this pdb file. If you link an

问题 When using PostSharp with a Referenced Assembly with proper PDB info( checked with chkmatch), it seems strange that the debug info gets lost by VStudio build and post compile process and I get the following error by using chkmatch to compare the assembly after the vstudio build. Error: Debug information not found in the executable. So it doesn't step into for debugging into this assembly. Does Post Sharp properly writes back the Assemblies without destroying the PDB location offset info as I