Breakpad - Crashandler for Linux, Windows and Mac #4778
Conversation
This file contains 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.
Breakpad claims to be a crash handler working for Linux, Windows and Mac
On crash it creates and documents a small file with all relevant information.
In order to get the reason this file has to be processed with google available tools.
See
https://chromium.googlesource.com/breakpad/breakpad/+/master/docs/linux_starter_guide.md
for short instructions
The intent of this is to find the reason for the segfaults in the mxe CI build of my indexed2 PR
But in general its valuable to have a crash handler in place which yields information where the crash has happened.
Lets see at first, if it works for linux