-
Notifications
You must be signed in to change notification settings - Fork 105
Fix out-of-bound access in clean_up_infeasibilities.
#346
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
This OOB access happens when the last element is the one being removed: the second access to `infeasibility_indices[k]` after the `pop_back` is invalid. This is another example for issue NVIDIA#150. Signed-off-by: Clement Courbet <courbet@google.com>
0b9eb2d to
1de0a95
Compare
|
/ok to test 1de0a95 |
|
/ok to test 9e81244 |
|
/ok to test d669466 |
|
🔔 Hi @anandhkb @legrosbuffle, this pull request has had no activity for 7 days. Please update or let us know if it can be closed. Thank you! If this is an "epic" issue, then please add the "epic" label to this issue. |
|
/merge |
This OOB access happens when the last element is the one being removed: the second access to `infeasibility_indices[k]` after the `pop_back` is invalid. This is another example for issue #150. Authors: - Clement Courbet (https://github.com/legrosbuffle) - Ramakrishnap (https://github.com/rgsl888prabhu) Approvers: - Rajesh Gandham (https://github.com/rg20) URL: #346
This OOB access happens when the last element is the one being removed: the second access to
infeasibility_indices[k]after thepop_backis invalid.This is another example for issue #150.