Skip to content

Fix potential use-after-free in emitFuncToBlock exposed by enabling o… #23218

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

gottesmm
Copy link
Contributor

…wnership verification on PrintAsObjC/blocks.swift.

If the block is guaranteed, we need to be sure to copy here. This can happen for
instance with arguments (where this was caught). I added a SILGen test that
exposes this failure since this is not an actual bug in PrintAsObjC.

…wnership verification on PrintAsObjC/blocks.swift.

If the block is guaranteed, we need to be sure to copy here. This can happen for
instance with arguments (where this was caught). I added a SILGen test that
exposes this failure since this is not an actual bug in PrintAsObjC.
@gottesmm gottesmm requested a review from jckarter March 11, 2019 21:24
@gottesmm
Copy link
Contributor Author

@swift-ci smoke test and merge

Copy link
Contributor

@jckarter jckarter left a comment

Choose a reason for hiding this comment

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

Nice catch!

@swift-ci swift-ci merged commit a6ec750 into swiftlang:master Mar 11, 2019
@gottesmm gottesmm deleted the pr-d24d308b6dec12e39ca8fb7df3726a8340b263fc branch March 12, 2019 05:50
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