Win32: Is there a difference between Dr. Watson's full / mini dumps and writing mine?

I have an application that sometimes crashes in release builds; unfortunately, it looks like it crashed into a third-party DLL. Trying to figure it out, I swam into the sea HOW RESULTS and descriptions of how Windows creates emergency dumps.

I was thinking about using this suggested mini dump:

Getting a dump of a process that crashes on startup

I planned to leave this functionality in the code, so a dump is always created for my application without first installing a PC. BTW, this application is not for distribution; it will be paired with our own hardware, so I don’t worry about random users who create dump files on their computers if the application crashes.

Note: all code is C / C ++.

Is there any difference between what Dr. Watson (drwtsn32.exe) and this code will produce for me?

+3
source share
4 answers

With Dr. Watson, you will only get dumps when the doctor sees that you are "crashed." Using the dump truck API, you can call it from anywhere in the application. For instance. you can transmute ordinary statements to discard, rather than show, a dialog. In my experience, when you have dump support in your application, it will be easier for you to track, fix and fix various problems, simply because you can create a full dump (or even a mini-drive) anywhere you think the code needs. .

+2

, , -, . Minidumps , , ( , ).

, , -, drwatson ( werfault Vista onwards) , . , . , , , -, , , , . - , , .

, , , , ADPlus - ​​ , , . , , , .

+1

, , MiniDumpWriteDump - . , , , .

MiniDumpWriteDump , Dr. Watson, , .

: MiniDumpWriteDump

+1

. Dr Watson -, ntsd debugger, , .

- Dr Watson , . , ntsd .

The only advantage of using DrWatson is that it is pre-installed on Windows.

0
source

Source: https://habr.com/ru/post/1742351/


All Articles