Skip to content

[4.2] JSONSerialization: fix a crash when an escape sequence contains low-s… #2027

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

Conversation

spevans
Copy link
Contributor

@spevans spevans commented Mar 20, 2019

…urrogate code point without the corresponding high-surrogate code point

(cherry picked from commit 9eca3c0)

…urrogate code point without the corresponding high-surrogate code point

(cherry picked from commit 9eca3c0)
@spevans
Copy link
Contributor Author

spevans commented Mar 20, 2019

@swift-ci test 4.2

@spevans spevans changed the title JSONSerialization: fix a crash when an escape sequence contains low-s… [4.2] JSONSerialization: fix a crash when an escape sequence contains low-s… Mar 20, 2019
@millenomi
Copy link
Contributor

I don't know that we have any more 4.2 release vehicles. @weissi?

@spevans: can this be cherry-picked to 5.0 if it isn't there?

@weissi
Copy link
Contributor

weissi commented Mar 30, 2019

@millenomi/@spevans I think that one is quite important so I think we could make a release for this soonish, let’s see if there are other important issues like this one coming in.

We should definitely also propose this PR for Swift 5. We’re starting to gear up the monthlies for Swift 5 🙌

@spevans
Copy link
Contributor Author

spevans commented Apr 1, 2019

@millenomi This one is already in 5.0, for all my cherry-picks to 4.2 I made sure they came from 5.0

@weissi I have a use after free to backport to 5.0 and potentially 4.2 #2038 and a leak from #1540 which might also be worth doing if there is going to be one last 4.2 release.

@millenomi
Copy link
Contributor

@spevans Please send 'em.

@millenomi millenomi merged commit f8429e0 into swiftlang:swift-4.2-branch Apr 1, 2019
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.

4 participants