[PLAT-8863] Fix crash when reporting internal errors during +[Bugsnag start]
#1474
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.
Goal
Fix a crash that could occur when reporting internal errors during
+[Bugsnag start]
.Regression introduced in #1435 / v6.21.0
Changeset
Initializes
BSGInternalErrorReporter
AFTERbsg_runContext
to ensure the latter is non-null.Considered moving
BSGRunContextInit
to a+initialize
method instead, but that would hinder testing - it would not be possible to setbsg_runContext
toNULL
and have it re-initialized when starting a newBugsnagClient
.Testing
Adds a unit test case that reproduced the problem and verifies the fix.