Source: stackoverflow.com --- Wednesday, October 11, 2017
I am using Microsoft Minidump feature so I can analyse crashes in released programs. http://ift.tt/1XHKZzDWindows/desktop/ee416349(v=vs.85).aspx The code is similar to answer for this stackoverflow question: How to write a sample code that will crash and produce dump file? Usually when I have a crash, I can open the crash dump file in Visual Studio and it will take me to the offending line of source code which makes troubleshooting these problems really easy. But sometimes it is not so easy. I have a crash dump file where I am not able to locate the offending source line. Why is that? What useful information can I get from this dump file? Any tips on finding the needle in the haystack? Here is what I am doing. I checkout the sources for this release by tag. I copy over the corresponding pdb files to the same folder as the crash dump - file is myprogram.exe.3140.dmp I then open the crash dump with the compiler used to build the exe, Visual Studio 2012. I then see some useful information: Last write time 10/10/2017 15:28:52 Process Architecture: x86 Exception Code 0xC0000005 Exception Information The tread tried to read from or write to a virtual address for which it does not have the appropriate access. Heap Information Present OS Version 6.1.7601 Modules: myprogram.exe 1.7.41.0 myprogram.dll 1.1.0.27 etc Then I click Debug with Native Only I then get the dialog: Unhandled exception at 0x548BFFD5 in myprogram. ...
from Windows http://ift.tt/2ygrObV
No comments:
Post a Comment