-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Runtime: add a non-Darwin error message storage #72785
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
From the Embedded Swift perspective: This change LGTM -- it doesn't change anything around Embedded Swift, as Errors.cpp is not part of the Embedded Swift Runtime. I think it's fine to proceed as is, because (1) Embedded Swift shouldn't get any any non-essential runtime facilities, (2) in production builds, it already today has fatalErrors() not print the error message, and the error message string is not even present in the binaries (to minimize codesize), (3) the crash message should be recoverable from debuginfo (4) given the highly experimental state of Embedded Swift, we can always revisit and change the status quo later. |
@swift-ci please test |
@swift-ci please test Windows platform |
@swift-ci please test |
This introduces a non-Darwin (non-CrashReporter) storage for error messages to allow extraction for crash reporting. This is initially meant to be used on Windows, though it is generic enough to be used on any platform.
@swift-ci please test |
@compnerd I am seeing a compilation error possibly due to this PR on ubuntu 18.04 : https://ci.swift.org/job/oss-swift-RA-lsan-linux-ubuntu-18_04/10040/console
|
@meg-gupta interesting; seems like it is an overload mismatch? It might require an explicit cast? I'll see if I can get away with casting away the const-ness on all the platforms. Is there an easy way to trigger the runs on the 18.04 builder? |
Mishal pointed me to https://github.com/apple/swift/blob/main/docs/ContinuousIntegration.md#build-swift-toolchain. You can use - |
This introduces a non-Darwin (non-CrashReporter) storage for error messages to allow extraction for crash reporting. This is initially meant to be used on Windows, though it is generic enough to be used on any platform.
Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.
Resolves #NNNNN, fix apple/llvm-project#MMMMM.