pdb-files

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 .exe .pdb The msvc C/C++ compiler supports it adequately. Recently the need to build a few static

Are there any VC++ settings I should know about to generate better PDB files that contain more information? I have a crash dump analysis system in place based on the project crashrpt . Also, my production build server has the source code installed on the D:\, but my development machine has the source code on the C:\. I entered the source path in the VC++ settings, but when looking through the call stack of a crash, it doesn't automatically jump to my source code. I believe if I had my dev machine's source code on the D:\ it would work. "Are there any VC++ settings I should know about" Make

Are there any security issues keeping the .NET PDB files on the real server? I know that throwing exceptions might take a bit longer , but who throws exceptions during normal execution anyway? :-) But from a security perspective? any issues? Hmm - I'd lean on the side of security caution on this. I think you should have PDBs, but not on production servers. Besides, you should have Debug turned off on any live system. Debug is nasty, and you just don't want it when you don't need it. From Scott Guthrie : The compilation of ASP.NET pages takes longer (since some batch optimizations are disabled)

LNK4099 warnings can occur when building on Windows during the link phase of a static compilation. E.g. when building using nmake and VC10 I get a stream of LNK4099 warnings like: libcurl_a_debug.lib(rc2_cbc.obj) : warning LNK4099: PDB 'lib.pdb' was not found with 'libcurl_a_debug.lib(rc2_cbc.obj)' or at 'C:\dev\scaler\center\dlux\lib.pdb'; linking object as if no debug info StackOverflow gives a good overview of the problem , but not the detail required to understand it. Rather than ignore the warning or disable the warning , I would like to fix the makefiles in my build to remove the problem

In order to be able to properly debug release builds a PDB file is needed. Can the PDB file become less usable when the compiler uses different kinds of optimizations (FPO, PGO, intrinsic functions, inlining etc.)? If so, is the effect of optimization severe or merely cause adjacent lines of code to get mixed up? (I'm using VC2005, and will always choose debugability over optimized performance - but the question is general) Yes, optimized code is less debuggable. Not only is some information missing, some information will be very misleading. The biggest issue in my opinion is local variables.

I have a lot of files in .pdb format, some of them downloaded, but until now I can't use or read what's inside, so I'm looking for how to read and view the .pdb file format from MS Windows XP. Any of you that may know how to open it? Eilon If you mean PDB as in a "program database" that the debugger uses: PDB files contain data about a file such as an EXE or DLL that is used to aid in debugging. There are public interfaces that allow you to extract data from the file. See examples here: http://blogs.msdn.com/jmstall/archive/2005/08/25/pdb2xml.aspx http://www.codeproject.com/KB/bugs/PdbParser

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