Can anyone direct me to any information on how I would go about obtaining usable information from a Windows Error Report? I'd like to be able to see what the offending call was and possibly a stack trace. TIA.
Can anyone direct me to any information on how I would go about obtaining usable information from a Windows Error Report? I'd like to be able to see what the offending call was and possibly a stack trace. TIA.
Open the dmp/mdmp in VS then start debugging it as you would a running program, or open it with windbg and use "!analyze -v" to get a stack track among other things for the faulting thread. If you built with VS then you'll need the symbols for the app to get any meaningful info from either debugger.
Thanks guys.
The Windows Error Reporting team also has a blog with some helpful information:
http://blogs.msdn.com/wer
Please let me know if you need any help getting setup on Winqual.
Best regards,
Kevin Hill (Program Manager, Windows Error Reporting)
Cool, I was wondering about that, but all of the literature on MSDN seems to imply that getting your own bucket for WER reports requires some doing (i.e. formal acceptance, company verisign)... what can the "little guy" still make use of WER?
It's not hard to sign up for free access to the MS error reporting database. BUT you'll need a digital certificate to prove to MS who you are and that you have a legitimate need to access the crash information.
You can add crash reporting to your applications by using unhandled exception filters.