-
Notifications
You must be signed in to change notification settings - Fork 351
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
[CRBTreeMap] Segmentation fault at Leetcode #1429 #51
Comments
alantudyk
changed the title
[Segmentation fault], Leetcode 1429
[CRBTreeMap, Segmentation fault], Leetcode 1429
Oct 15, 2023
alantudyk
changed the title
[CRBTreeMap, Segmentation fault], Leetcode 1429
[CRBTreeMap] Segmentation fault at Leetcode #1429
Oct 15, 2023
I can confirm that deleting a non-existent element causes a segmentation fault sometimes. If you run |
Causes seg fault with ruby 3.2.2
|
A similar issue exists inside RubyRBTreeMap
|
I have a fix waiting for a PR review. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Only 1 line is different:
OK: https://leetcode.com/submissions/detail/1075862918/
@t.delete p if @t[p]
Not OK: https://leetcode.com/submissions/detail/1075860617/
@t.delete p
The text was updated successfully, but these errors were encountered: