Skip to content
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

[backport to 3.6] bpo-29438: fixed use-after-free in key sharing dict #39

Merged
merged 1 commit into from
Feb 13, 2017

Conversation

methane
Copy link
Member

@methane methane commented Feb 12, 2017

No description provided.

@methane methane added the type-bug An unexpected behavior, bug, or error label Feb 12, 2017
@methane methane changed the title bpo-29438: fixed use-after-free in key sharing dict [backport to 3.6] bpo-29438: fixed use-after-free in key sharing dict Feb 12, 2017
@@ -10,6 +10,8 @@ What's New in Python 3.6.1 release candidate 1?
Core and Builtins
-----------------

- bpo-29438: Fixed use-after-free problem in key sharing dict.
Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure about "bpo-" in Misc/NEWS and commit message, but if this is correct the patch LGTM.

Copy link
Member Author

Choose a reason for hiding this comment

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

@methane methane merged commit 89ddffb into python:3.6 Feb 13, 2017
@methane methane deleted the bpo29438/py36 branch February 13, 2017 00:19
jaraco pushed a commit that referenced this pull request Dec 2, 2022
Only add the branch prefix to the PR title.

Use cherry_picker v0.2.4

Closes python/miss-islington#38
oraluben pushed a commit to oraluben/cpython that referenced this pull request Jun 25, 2023
* fix: handle when a single BB may have multiple jump targets

* nit: remove wrong comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants