windows-error-reporting

How to analyse WERInternalMetadata.xml file generated by Windows Crash Reporter?

为君一笑 提交于 2019-11-29 03:41:05
A .Net 4.0 app keeps crashing for a user, but just for him, I could not reproduce the bug. He attached the WERInternalMetadata.xml file generated by the Windows Crash Reporter. By opening it I found out that it's a System.IO.FileNotFoundException that crashes the software, however, there are no functions called in that function that would throw that kind of exception, so the is problem somewhere else or deeper. This is the "most interesting" part of the file. It contains (hexadecimal) numbers, but I couldn't find out what they mean. <ProblemSignatures> <EventType>CLR20r3</EventType>

How to analyse WERInternalMetadata.xml file generated by Windows Crash Reporter?

谁说胖子不能爱 提交于 2019-11-27 17:43:55
问题 A .Net 4.0 app keeps crashing for a user, but just for him, I could not reproduce the bug. He attached the WERInternalMetadata.xml file generated by the Windows Crash Reporter. By opening it I found out that it's a System.IO.FileNotFoundException that crashes the software, however, there are no functions called in that function that would throw that kind of exception, so the is problem somewhere else or deeper. This is the "most interesting" part of the file. It contains (hexadecimal) numbers

How do I disable the &#39;Debug / Close Application&#39; dialog on Windows Vista?

蹲街弑〆低调 提交于 2019-11-26 12:42:28
When an application crashes on Windows and a debugger such as Visual Studio is installed the following modal dialog appears: [Title: Microsoft Windows] X has stopped working A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. [Debug][Close Application] Is there a way to disable this dialog? That is, have the program just crash and burn silently? My scenario is that I would like to run several automated tests, some of which will crash due to bugs in the application under test. I don't want these dialogs stalling the

Windows does not produce full crash dumps even though registry is set correctly

青春壹個敷衍的年華 提交于 2019-11-26 07:47:33
问题 My client are experiencing software crashes with a VB6 program I wrote. I had set up the registry to produce full crash dumps, and I saw it working correctly with other programs that crashed on their system, but for some reason, for my program, it stil creates the simple crash dumps in a totally different directory. My program is 32 bit running on an x64 computer. I have setup the registry as shown in the picture, both for SOFTWARE\\Microsoft and SOFTWARE\\Wow6432Node\\Microsoft. Still doesn\

How do I disable the &#39;Debug / Close Application&#39; dialog on Windows Vista?

不想你离开。 提交于 2019-11-26 03:04:29
问题 When an application crashes on Windows and a debugger such as Visual Studio is installed the following modal dialog appears: [Title: Microsoft Windows] X has stopped working A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. [Debug][Close Application] Is there a way to disable this dialog? That is, have the program just crash and burn silently? My scenario is that I would like to run several automated tests, some