Closed rconde01 closed 4 years ago
Hi, @rconde01!
Indeed, the stack trace looks like it's an issue with the C++ Build Insights SDK. Thank you for posting it in Microsoft's forums and providing the link here.
What we can do, on our end, is handling the possible exceptions in the SDK and show an error with the full stack. Something like #4.
I'll leave this issue on hold and monitor your linked post in Developer Community.
Hello, @rconde01!
Just a quick update: While there's no word from the C++ Build Insights SDK (so this issue isn't yet fixed), your report helped me provide a way for users to include extra information when reporting crashes.
We now generate MiniDumps when crashing, as part of #30. I've made it crash the way this issue does and this is the sample MiniDump:
CppBuildAnalyzer_20200519_121745.zip. Requires .exe
and .pdb
from commit 57f3d78.
I'm still leaving this issue on hold until we get an updated SDK with the fix. Thank again!
MS has a patch on deck: https://github.com/microsoft/cpp-build-insights-samples/issues/5
cool - hopefully that does it.
Thanks for the heads up!
I've upgraded the SDK to v1.1.0
successfully and I'm no longer able to reproduce the crash.
Can you please check with the linked Pull Request?
Thank you!
Works for me now - closing.
I successfully generated my trace file, but got a crash when i go to analyze it. The call stack is:
The trace file is ~1GB but the memory of CppBuildAnalyzer is only 100MB when it crashes.