<p>I have heard using PDB files can help diagnose where a crash occurred.<br>
My <em>basic</em> understanding is that you give Visual studio the source file, the pdb file and the crash information (from Dr Watson?)<br>
Can someone please explain how it all works / what is involved?
(Thank you!)</p>

[{'answer_id': 72130, 'author': 'Omer van Kloeten', 'author_id': 4979, 'author_profile': 'https://Stackoverflow.com/users/4979', 'pm_score': 5, 'selected': False, 'text': "<p>PDB files map an assembly's MSIL to the original source lines. This means that if you put the PDB that was compiled with the assembly in the same directory as the assembly, your exception stack traces will have the names and lines of the positions in the original source files. Without the PDB file, you will only see the name of the class and method for each level of the stack trace.</p>\n"}, {'answer_id': 72190, 'author': 'roo', 'author_id': 716, 'author_profile': 'https://Stackoverflow.com/users/716', 'pm_score': 6, 'selected': True, 'text': '<p>PDB files are generated when you build your project. They contain information relating to the built binaries which Visual Studio can interpret.</p>\n\n<p>When a program crashes and it generates a crash report, Visual Studio is able to take that report and link it back to the source code via the PDB file for the application. PDB files must be built from the same binary that generated the crash report!</p>\n\n<p>There are some issues that we have encountered over time.</p>\n\n<ul>\n<li>The machine that is debugging the crash report needs to have the source on the same path as the machine that built the binary.</li>\n<li>Release builds often optimize to the extent where you cannot view the state of object member variables</li>\n</ul>\n\n<p>If anyone knows how to defeat the former, I would be grateful for some input.</p>\n'}, {'answer_id': 134939, 'author': 'lesscode', 'author_id': 18482, 'author_profile': 'https://Stackoverflow.com/users/18482', 'pm_score': 4, 'selected': False, 'text': '<p>You should look into setting up a symbol server and indexing the PDB files to your source code control system. I just recently went through this process for our product and it works very well. You don\'t have to be concerned about making PDB files available with the binaries, nor how to get the appropriate source code when debugging dump files.</p>\n\n<p>John Robbins\' book: <a href="https://rads.stackoverflow.com/amzn/click/com/0735622027" rel="nofollow noreferrer" rel="nofollow noreferrer">http://www.amazon.com/Debugging-Microsoft-NET-2-0-Applications/dp/0735622027/ref=pd_bbs_sr_1?ie=UTF8&amp;s=books&amp;qid=1222366012&amp;sr=8-1</a></p>\n\n<p>Look here for some sample code for generating minidumps (which don\'t have to be restricted to post-crash analysis -- you can generate them at any point in your code without crashing): <a href="http://www.codeproject.com/KB/debug/postmortemdebug_standalone1.aspx" rel="nofollow noreferrer">http://www.codeproject.com/KB/debug/postmortemdebug_standalone1.aspx</a></p>\n'}]
['https://Stackoverflow.com/questions/72104', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/3590/']