Repository navigation
Crash reports: minidump, log copy and a chosen folder - #35
Merged
Merged
Conversation
A crash now writes a crash-<time> folder with crash.txt, a copy of flex.log and, on Windows, flex.dmp, in Settings → Crash reports folder (or the logs folder). --test-crash checks it works. CI keeps flex.pdb so the dumps can be read.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For tracking down the occasional crash on Windows (especially leaving fullscreen with the zoom-out button).
crash-<date-time>folder holdingcrash.txt(what happened and where), a copy offlex.logand, on Windows, a minidumpflex.dmp.flex.exe --test-crashcrashes on purpose after 5 seconds, to check the setup.flex.pdb(exe size unchanged) with the build artifacts. Tagged releases also attachflex-vX.Y.Z-symbols.zipso the dumps can be read.Tested on macOS (panic path, default and chosen folder). The Windows build cross-compiles and links
MiniDumpWriteDump. The native Windows path and the CI symbol packaging are untested until this runs on Windows.Not caught: fail-fast aborts (
0xC0000409) and some heap corruption skip in-process handlers. Windows Error Reporting LocalDumps covers those.