[Linux] Disable fatalError() backtraces when the runtime backtracer is active. #69570
Conversation
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
…s active. There's no need for fatalError() to try to generate its own backtraces when the runtime's backtracer is enabled. Not only is the code it uses more fragile but it also doesn't support async or inline frames and it can't look-up symbols properly either. rdar://117470489
Contributor
Author
|
@swift-ci Please smoke test |
The Runtime/backtrace test is a test of the fatalError() backtracer, which gets turned off when we have the new backtracer enabled. So, to make this test work, we need to turn off the new backtracer. rdar://117470489
Contributor
Author
|
@swift-ci Please smoke test |
mikeash
approved these changes
Nov 1, 2023
glessard
approved these changes
Nov 1, 2023
This was referenced Nov 2, 2023
Contributor
Author
|
@swift-ci Please smoke test |
When backtracing is disabled, don't try to refer to `_swift_backtraceSettings`. rdar://117470489
al45tair
force-pushed
the
eng/PR-117470489
branch
from
eeaccee to
003b455
Compare
Contributor
Author
|
@swift-ci Please smoke test |
Contributor
Author
|
@swift-ci Please smoke test Windows platform. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
There's no need for fatalError() to try to generate its own backtraces when the runtime's backtracer is enabled. Not only is the code it uses more fragile but it also doesn't support async or inline frames and it can't look-up symbols properly either.
rdar://117470489