1

I've asked this question on the SuperUser forum, but there I was redirected here, can anybody help me?

Hereby a copy of my question:

I am facing a crash on a Windows system at customer premises. I had such situations regularly in the past when I was working for customers with UNIX computers. In that case, I only needed to investigate the core files and I knew about where the crash has happened.

Does such a system exist for Windows environment, and in case yes, how does it work and on which Windows systems is it supported? (I've been looking on the internet but the only dumps (cores) I've found where the ones where the whole Windows system crashes, not just a program)

Dominique
  • 16,450
  • 15
  • 56
  • 112
  • Yes, the proper word to google is "minidump". – Hans Passant Sep 16 '16 at 11:45
  • Minidumps aren't written automatically by applications upon crashing. You'll either have to set up an unhandled exception filter and call [MiniDumpWriteDump](https://msdn.microsoft.com/en-us/library/windows/desktop/ms680360.aspx), or set up [Windows Error Reporting](https://msdn.microsoft.com/en-us/library/windows/desktop/bb513641.aspx) to [collect user-mode dumps](https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181.aspx) (Server 2008/Vista SP1 and above). – IInspectable Sep 16 '16 at 11:56

1 Answers1

0

The equivalent of a core dump on Windows is a minidump. It has the .dmp file extension and can e.g. be opened in Visual Studio or in WinDbg.

There are many ways of getting such a crash dump. I once answered How do I take a good crash dump for .NET?, but most of that can also be applied to C++ and VB6.

Java has it's own way of reporting crashes and interpreted languages like Python, too.

Community
  • 1
  • 1
Thomas Weller
  • 55,411
  • 20
  • 125
  • 222