Repository navigation
Log unhandled exceptions to Rapr.log - #482
Merged
Merged
Conversation
When the app crashed at startup (lostindark#479) the log only said "Rapr started", so the cause had to be dug out of the Windows event log. Write any unhandled exception to the trace log before the process goes down. UI-thread exceptions still show the standard WinForms error dialog; they are just logged first.
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.
When the app crashed at startup in #479, Rapr.log only said "Rapr started", so the cause had to come from the Windows event log. This writes any unhandled exception to the trace log before the process ends.
No new strings.