Skip to content

[Serialization] Fix deserialization crash occurring when a mixed framework fails to load its ObjC part. #4028

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

Merged
merged 1 commit into from
Aug 5, 2016

Conversation

akyrtzi
Copy link
Contributor

@akyrtzi akyrtzi commented Aug 4, 2016

Fixes crash with a case such as:

  • there is mixed framework A
  • swift module B depends on A and is built fine
  • there is a swift invocation that imports B but causes the ObjC part of A to fail to import
  • trying to serialize decls of B that depend on A will crash

rdar://27709042


Before merging this pull request to apple/swift repository:

  • Test pull request on Swift continuous integration.

Triggering Swift CI

The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:

Smoke Testing

Platform Comment
All supported platforms @swift-ci Please smoke test
All supported platforms @swift-ci Please smoke test and merge
OS X platform @swift-ci Please smoke test OS X platform
Linux platform @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

  1. Builds the compiler incrementally.
  2. Builds the standard library only for macOS. Simulator standard libraries and
    device standard libraries are not built.
  3. lldb is not built.
  4. The test and validation-test targets are run only for macOS. The optimized
    version of these tests are not run.

A smoke test on Linux does the following:

  1. Builds the compiler incrementally.
  2. Builds the standard library incrementally.
  3. lldb is built incrementally.
  4. The swift test and validation-test targets are run. The optimized version of these
    tests are not run.
  5. lldb is tested.

Validation Testing

Platform Comment
All supported platforms @swift-ci Please test
All supported platforms @swift-ci Please test and merge
OS X platform @swift-ci Please test OS X platform
OS X platform @swift-ci Please benchmark
Linux platform @swift-ci Please test Linux platform

Lint Testing

Language Comment
Python @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

…ework fails to load its ObjC part.

rdar://27709042
@akyrtzi
Copy link
Contributor Author

akyrtzi commented Aug 4, 2016

@swift-ci smoke test

@jrose-apple
Copy link
Contributor

%target-swift-frontend already includes a per-test module cache path, so the manual -module-cache-path %t/mcp isn't necessary. Looks good other than that.

@akyrtzi
Copy link
Contributor Author

akyrtzi commented Aug 5, 2016

The %target-swift-frontend module cache is actually per test suite run, and for this test I slightly preferred to not 'pollute' that cache.

@akyrtzi
Copy link
Contributor Author

akyrtzi commented Aug 5, 2016

@swift-ci smoke test linux platform

@akyrtzi
Copy link
Contributor Author

akyrtzi commented Aug 5, 2016

The linux lldb failure is showing in the bots, it's unrelated with this change.

@akyrtzi akyrtzi merged commit f3af4ae into swiftlang:master Aug 5, 2016
@akyrtzi akyrtzi deleted the deserialization-crash-27709042 branch August 5, 2016 03:36
@akyrtzi akyrtzi restored the deserialization-crash-27709042 branch August 5, 2016 03:37
// RUN: cp %S/Inputs/MixModA.modulemap %t/MixModA.framework/Modules/module.modulemap

// RUN: %target-swift-frontend -emit-module %S/Inputs/SwiftModA.swift -module-name MixModA -I %S/Inputs/objcfail -o %t/MixModA.framework/Modules/MixModA.swiftmodule/x86_64.swiftmodule -emit-objc-header -emit-objc-header-path %t/MixModA.framework/Headers/MixModA-Swift.h -module-cache-path %t/mcp
// RUN: %target-swift-frontend -emit-module %S/Inputs/SwiftModB.swift -module-name SwiftModB -F %t -o %t -module-cache-path %t/mcp
Copy link
Member

@rintaro rintaro Aug 5, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

x86_64 should be %target-cpu
x86_64.swiftmodule should be %target-swiftmodule-name
PR: #4043

@akyrtzi akyrtzi deleted the deserialization-crash-27709042 branch January 8, 2019 06:21
kateinoigakukun pushed a commit that referenced this pull request Aug 31, 2022
[pull] swiftwasm from main
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants