Sometimes it happens that your distributed application crashes on customer machines. What you obtain as an info from the customer is that the application simply crashed "doing something": no way to understand where the bug was in your code. Is there a library/add-on to be linked to your application that can create a backtrace file/crash dump report so that it could be sent by the customer to better understand what you normally see in the Visual Studio call stack helping understanding where the bug is?
Asked
Active
Viewed 2,991 times
0
-
All versions of Windows starting from XP. The C++ application is compiled in release mode – ABCplus Aug 20 '14 at 09:46
-
Fix the tags of your question then. – trojanfoe Aug 20 '14 at 09:48
-
Post-Mortem Debugging: http://www.codeproject.com/Articles/1934/Post-Mortem-Debugging-Your-Application-with-Minidu – Alex F Aug 20 '14 at 09:49
-
there is a simple way to create crush dump files see: https://stackoverflow.com/a/54211155/8740349 – Top-Master Jan 16 '19 at 06:03
2 Answers
2
There are a few third party solutions available that provide a library of functions to trap crash data. A simple google search should suffice. However, depending on your budget, the easiest solution is to create a Microsoft WER account. WER has advantages over the other solutions because it is part of the OS and it exposes several functions that allow you to tailor the crash data collection.
rrirower
- 4,338
- 4
- 27
- 45
2
see google: https://code.google.com/p/google-breakpad/
Description from the website:
Breakpad is a library and tool suite that allows you to distribute an application to users with compiler-provided debugging information removed, record crashes in compact "minidump" files, send them back to your server, and produce C and C++ stack traces from these minidumps. Breakpad can also write minidumps on request for programs that have not crashed.
https://code.google.com/p/google-breakpad/wiki/GettingStartedWithBreakpad
cageman
- 333
- 2
- 10