gh-120378: Fix crash caused by integer overflow in curses#124555
gh-120378: Fix crash caused by integer overflow in curses#124555vstinner merged 10 commits intopython:mainfrom
curses#124555Conversation
|
cc @picnixz |
|
I'll have a look after sleeping a bit. By the way, instead of cc'ing me, you can just outright request a review from me when you know I've been active on the corresponding issue (I'll reject it if I deem myself not enough an expert). |
I was under the impression that requesting a review didn't result in a notification, good to know! |
picnixz
left a comment
There was a problem hiding this comment.
Does the resize_term function also suffer from the same issue?
Misc/NEWS.d/next/Library/2024-09-25-18-07-51.gh-issue-120378.NlBSz_.rst
Outdated
Show resolved
Hide resolved
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
It does, but it seems that this patch fixes the issue for both of them. I guess I'll test for it too. |
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
…python into curses-int-limit
Misc/NEWS.d/next/Library/2024-09-25-18-07-51.gh-issue-120378.NlBSz_.rst
Outdated
Show resolved
Hide resolved
…lBSz_.rst Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
|
Ok, by the way I know why we export unconditionally the method. Actually, it would be a no-op if the method is not available (see the clinic generated code which does |
|
I think I fixed it by moving that test, anyway. Anything else to do here? |
No, nothing else to do! (at least AFAICT). |
|
Now, time to find a core dev to review this. I don't think we have anyone active that's worked much on curses, do we? |
|
No, but Victor has been reviewing my curses (and not my cursed) PRs so I think we can ask him. |
|
Thanks @ZeroIntensity for the PR, and @vstinner for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13. |
…thonGH-124555) This is actually an upstream problem in curses, and has been reported to them already: https://lists.gnu.org/archive/html/bug-ncurses/2024-09/msg00101.html This is a nice workaround in the meantime to prevent the segfault. (cherry picked from commit c2ba931) Co-authored-by: Peter Bierma <zintensitydev@gmail.com> Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
|
Sorry, @ZeroIntensity and @vstinner, I could not cleanly backport this to |
|
GH-124905 is a backport of this pull request to the 3.13 branch. |
|
@ZeroIntensity: If you consider that backporting to 3.12 is worth it, would you mind to try to backport the change manually? The automated backport failed. |
|
PR merged, thank you @ZeroIntensity. I'm not really super happy about this workaround, but it seems like upstream is not responsive on this crash. |
Yeah, I can do that a little later today. It's odd that it worked for 3.13 but not 3.12, though. |
This could be a clinic issue (where the generator changed between 3.12 and 3.13 and introduced conflicts). |
…es` (pythonGH-124555) This is actually an upstream problem in curses, and has been reported to them already: https://lists.gnu.org/archive/html/bug-ncurses/2024-09/msg00101.html This is a nice workaround in the meantime to prevent the segfault. (cherry picked from commit c2ba931) Co-authored-by: Peter Bierma <zintensitydev@gmail.com> Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
|
GH-124911 is a backport of this pull request to the 3.12 branch. |
Oh, the email was sent last week :-) So it's early to say that upstream is not responsive, sorry about that. |
…H-124555) (#124911) This is actually an upstream problem in curses, and has been reported to them already: https://lists.gnu.org/archive/html/bug-ncurses/2024-09/msg00101.html This is a nice workaround in the meantime to prevent the segfault. (cherry picked from commit c2ba931) Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
…H-124555) (#124905) gh-120378: Fix crash caused by integer overflow in `curses` (GH-124555) This is actually an upstream problem in curses, and has been reported to them already: https://lists.gnu.org/archive/html/bug-ncurses/2024-09/msg00101.html This is a nice workaround in the meantime to prevent the segfault. (cherry picked from commit c2ba931) Co-authored-by: Peter Bierma <zintensitydev@gmail.com> Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
This is actually an upstream problem in
curses, and has been reported to them already. This is a nice workaround in the meantime to prevent the segfault.