zeroshade commented on PR #513: URL: https://github.com/apache/arrow-go/pull/513#issuecomment-3321435402
That is technically correct, though the checks don't look in C/C++ memory. Essentially, as long as we don't attempt to store `ArrowArray.buffers[2]` into a Go variable when it's not a valid pointer (which I believe we successfully avoid now) we should be safe because you only find the bad pointer by first dereferencing the void** in `ArrowArray.buffers`. If we do manage to hit this still, then we can look into adding a check in the trampoline function we have -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
