Started implementing a way of dealing with C++ Build Insights SDK crashes as mentioned in #4.
Tried to capture the stack trace and show it in console so users could paste it when reporting an issue.
However, after investigating about exceptions, SEH exceptions, __try __except and the like, no solution would provide enough information for a nice report.
Then I read about MiniDump and decided to add it to the project.
I've created a handler for unhandled exceptions called GenerateMiniDump (defined in its own MiniDumpGeneration file) that creates a .dmp file.
Users can then report the crash and include that file so we can investigate further.
Started implementing a way of dealing with C++ Build Insights SDK crashes as mentioned in #4. Tried to capture the stack trace and show it in console so users could paste it when reporting an issue.
However, after investigating about exceptions, SEH exceptions,
__try __exceptand the like, no solution would provide enough information for a nice report.Then I read about MiniDump and decided to add it to the project.
I've created a handler for unhandled exceptions called
GenerateMiniDump(defined in its ownMiniDumpGenerationfile) that creates a.dmpfile. Users can then report the crash and include that file so we can investigate further.