Crash reporting and RelWithDebInfo - #2366
Draft
JulianGro wants to merge 13 commits into
Draft
Conversation
JulianGro
force-pushed
the
RelWithDebInfo
branch
2 times, most recently
from
July 17, 2026 19:29
4fecacf to
542027d
Compare
JulianGro
marked this pull request as ready for review
July 17, 2026 20:08
JulianGro
marked this pull request as draft
July 22, 2026 13:57
JulianGro
force-pushed
the
RelWithDebInfo
branch
from
August 3, 2026 10:12
d8a6f4d to
c73dcf6
Compare
JulianGro
force-pushed
the
RelWithDebInfo
branch
from
August 3, 2026 10:26
c73dcf6 to
5244e15
Compare
JulianGro
force-pushed
the
RelWithDebInfo
branch
from
August 10, 2026 15:55
270da3a to
c3c2cb9
Compare
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.
Idea behind this PR is to bring back crash reporting, but in a way that yields actually useful crash reports.
In the past, we would collect crash reports, but without debug information and with the builds fully optimized. This would essentially only tell us that someone was crashing.
Now I want to create RelWithDebInfo builds, automatically upload the debug information to Sentry, and strip the debug symbols in the later packaging step.
Conan recipe change: overte-org/overte-conan-recipes#59
I tested the Sentry uploading locally using
act, since Pull Requests cannot usually access secrets.Known issues:
Maybe this was broken during the Application.cpp refactor?
Crashpad_handler starts successfully afterward.
Crash reporting can still be enabled in the general settings.
Enabling crash reporting in the settings somehow fixes the issue as well.
Todo:
OVERTE_USE_SENTRY