Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » C/C++ » Automation   (RSS)
Sorry, but there are no more tags available to filter with.
For a reference, here are some links to the previous parts in this series: · Prolific Usage of MiniDumpWriteDump · Opening a Crash Dump File · Getting the Stack from a .DMP File · Getting the Crash Details from a .DMP File · Showing the Disassembly from Read More...
When investigating a crash, it can often be beneficial to see the assembly leading up too, and even following the event. It turns out that generating the corresponding assembly at an address is pretty easy. The hard part is finding a good starting point Read More...
Aside from a stack trace (the "where"), you probably want to know something about the crash (the "why" or the "how"). With the code below, we can query some of the basic details about what happened. From this we will at least be able to determine if the Read More...
So now that we have a memory dump file , and know how to open it , we will want to pull some useful data out. To start with, we will grab the stack trace (which is arguably one of the more important pieces). And in case you've stumbled across the "dumpstk" Read More...
So let's assume for the moment that you have a collection of crash dump files from your team's application. These files may be generated from your stress tests, betas, etc. But where they come from really isn't important, what is important is that we Read More...
As a precursor to a series on programmatically querying crash dump files, I wanted to first talk about the MiniDumpWriteDump function. You don't necessarily need to wait for your application to crash in order to generate a memory dump. As soon as you Read More...
Throughout the software development cycle there is a wide array of areas where you need to generate various reports which include nifty looking charts. Whether you are generating performance reports, bug trends, tracking memory or CPU utilization, or Read More...
 
Page view tracker