-
-
Notifications
You must be signed in to change notification settings - Fork 8.4k
unix: avoid crashing after heap lock in REPL #17965
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
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #17965 +/- ##
=======================================
Coverage 98.38% 98.38%
=======================================
Files 171 171
Lines 22296 22296
=======================================
Hits 21937 21937
Misses 359 359 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Code size report:
|
Signed-off-by: Jeff Epler <jepler@gmail.com>
This is intended to be equivalent to the unlock in shared/runtime/pyexec.c. Signed-off-by: Jeff Epler <jepler@gmail.com>
Signed-off-by: Jeff Epler <jepler@gmail.com>
Signed-off-by: Jeff Epler <jepler@gmail.com>
3bad046
to
5c804a4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will clash somewhat with #12802. But the PR here makes a good (small) step in the right direction, and adds a good test, so we can merge it.
Summary
Closes: #17934
There were 3 distinct scenarios I ran into:
prompt_write_history
.Lock the heap, then type a long line:
Testing
I manually tested each variation I had discovered. I also added a CI-time test though I'm not 100% sure it's correct.