pdb-files | 易学教程

Release generating .pdb files, why?

阅读更多关于 Release generating .pdb files, why?

Why does Visual Studio 2005 generate the .pdb files when compiling in release? I won't be debugging a release build, so why are they generated? Cody Gray Because without the PDB files, it would be impossible to debug a "Release" build by anything other than address-level debugging. Optimizations really do a number on your code, making it very difficult to find the culprit if something goes wrong (say, an exception is thrown). Even setting breakpoints is extremely difficult, because lines of source code cannot be matched up one-to-one with (or even in the same order as) the generated assembly

What is a PDB file?

阅读更多关于 What is a PDB file?

问题 What is a PDB file and how can I exclude it from the release folder when I rebuild my solution? 回答1: A PDB file contains information for the debugger to work with. There's less information in a Release build than in a Debug build anyway. But if you want it to not be generated at all, go to your project's Build properties, select the Release configuration, click on "Advanced..." and under "Debug Info" pick "None". 回答2: I had originally asked myself the question " Do I need a PDB file deployed

Release generating .pdb files, why?

阅读更多关于 Release generating .pdb files, why?

问题 Why does Visual Studio 2005 generate the .pdb files when compiling in release? I won\'t be debugging a release build, so why are they generated? 回答1: Because without the PDB files, it would be impossible to debug a "Release" build by anything other than address-level debugging. Optimizations really do a number on your code, making it very difficult to find the culprit if something goes wrong (say, an exception is thrown). Even setting breakpoints is extremely difficult, because lines of

Preventing referenced assembly PDB and XML files copied to output

阅读更多关于 Preventing referenced assembly PDB and XML files copied to output

问题 I have a Visual Studio 2008 C#/.NET 3.5 project with a post build task to ZIP the contents. However I\'m finding that I\'m also getting the referenced assemblies\' .pdb (debug) and .xml (documentation) files in my output directory (and ZIP). For example, if MyProject.csproj references YourAssembly.dll and there are YourAssembly.xml and YourAssembly.pdb files in the same directory as the DLL they will show up in my output directory (and ZIP). I can exclude *.pdb when ZIP\'ing but I cannot

How to generate gcc debug symbol outside the build target?

阅读更多关于 How to generate gcc debug symbol outside the build target?

问题 I know I can generate debug symbol using -g option. However the symbol is embeded in the target file. Could gcc generate debug symbol outside the result executable/library? Like .pdb file of windows VC++ compiler did. 回答1: You need to use objcopy to separate the debug information: objcopy --only-keep-debug "${tostripfile}" "${debugdir}/${debugfile}" strip --strip-debug --strip-unneeded "${tostripfile}" objcopy --add-gnu-debuglink="${debugdir}/${debugfile}" "${tostripfile}" I use the bash