Debugging a kdmp file retrieved from your device.


I saw a post on one of our development forums asking how to debug a crash dump file (e.g. foo.kdmp). This is one of those things that is easy once you know how to do it, but you just can’t figure out how to get started. What you need to do is open the .kdmp file as a project. Pressing F5 after you open the dump will start a debug session, and drop you at the point your application crashed. Obviously you can’t modify any state, but it can be incredibly useful to see what state you were in when your app crashed. There’s a little information about Watson on Windows Mobile here: http://blogs.msdn.com/hopperx/archive/2005/10/07/478306.aspx. Cheers!


Comments (1)

  1. Ben says:

    I’ve never gotten this to work. Opening the dump as a solution works fine, but after hitting F5 all of the debug windows (modules, threads, etc.) are empty and nothing ever happens. Same thing with five or six different dump files.

    *shrug* Maybe the dumps are being created correctly? Oh well, thanks for the instructions anyhow! 🙂