-
Notifications
You must be signed in to change notification settings - Fork 484
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
Handle bug round 2 #1573
Labels
Comments
14 tasks
dgmcdona
added a commit
that referenced
this issue
Jan 31, 2025
An `InvalidAddressException` can occur inside of `__iter__` when iterating over the handle table (the exact exception occurs when creating the subtype in `objects.Array.__getitem__`. This changes the handle code to do a manual iteration over the sequence using the array length and indexes, catching the exception, logging the index, and continuing. In the test sample that prompted this change, the exception occurred on the access of the very last item in the array. closes #1573
dgmcdona
added a commit
that referenced
this issue
Jan 31, 2025
An `InvalidAddressException` can occur inside of `__iter__` when iterating over the handle table (the exact exception occurs when creating the subtype in `objects.Array.__getitem__`. This changes the handle code to do a manual iteration over the sequence using the array length and indexes, catch the exception, log the index, and continue. In the test sample that prompted this change, the exception occurred on the access of the very last item in the array. closes #1573
dgmcdona
added a commit
that referenced
this issue
Jan 31, 2025
An `InvalidAddressException` can occur inside of `__iter__` when iterating over the handle table (the exact exception occurs when creating the subtype in `objects.Array.__getitem__`. This changes the handle code to do a manual iteration over the sequence using the array length and indexes, catch the exception, log the index, and continue. In the test sample that prompted this change, the exception occurred on the access of the very last item in the array. closes #1573
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I triggered the backtrace at the bottom of the ticket on latest develop.
I know a bunch of stuff was fixed here, so this looks like something that maybe wasn't reachable before due to the other bugs. This code is so complicated I don't want to break it, but it looks like maybe individual elements of the array being bad (pointers?) could trigger it. If thats the case just make sure we continue past the bad ones in the fix.
Sample: Win2016x64_14393.lime.raw
The text was updated successfully, but these errors were encountered: