Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am using Sqlite on a production server but getting into deadlock scenarios. I compiled the System.Data.Sqlite.org dll in debug mode and the deadlocks went away (Of course they did..)
Now, since we are compiled in debug mode, every once and a while I am getting assertion failures.. These apparently just come up as a dialog and don’t get logged anywhere?
Is there a way, possibly with DebugDiag or another tool, to create a memory dump when the assertion failure happens?
Use MiniDumpWriteDump: http://msdn.microsoft.com/en-us/library/windows/desktop/ms680360%28v=vs.85%29.aspx and set the appropriate flags to enable all the relevant information to be written into the dump.
It is possible for you to tell Windows to do this for you by setting a registry key and there is adplus and procdump, see related question: crash generate dump and this: Generate dump with unmanaged code crash?