Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<blockquote> <p>4) Writig a log shows that the crash happen on a declaration of a local int variable! how could that be? Memory corruption?</p> </blockquote> <p>What is the underlying code in the executable / assembly? Declaration of int is no code at all, and as such cannot crash. Do you initialize the int somehow?</p> <p>To see the code where the crash happened you should perform what is called a postmortem analysis.</p> <h2>Windows Error Reporting</h2> <p>If you want to analyse the crash, you should get a crash dump. One option for this is to register for Windows Error Reporting - requires some money (you need a digital code signing ID) and some form filling. For more visit <a href="https://winqual.microsoft.com/" rel="nofollow noreferrer">https://winqual.microsoft.com/</a> .</p> <h2>Get the crash dump intended for WER directly from the customer</h2> <p>Another option is to get in touch witch some user who is experiencing the crash and get a crash dump intended for WER from him directly. The user can do this when he clicks on the Technical details before sending the crash to Microsoft - the crash dump file location can be checked there.</p> <h2>Your own minidump</h2> <p>Another option is to register your own exception handler, handle the exception and write a minidump anywhere you wish. Detailed description can be found at <a href="http://www.codeproject.com/KB/debug/postmortemdebug_standalone1.aspx" rel="nofollow noreferrer">Code Project Post-Mortem Debugging Your Application with Minidumps and Visual Studio .NET article</a>.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload