lidavidm commented on issue #405: URL: https://github.com/apache/arrow-go/issues/405#issuecomment-2979469631
This happened to ADBC before and ended up being because uninitialized data on the stack happened to be a leftover Go pointer because C++ code didn't zero-initialize a stack-allocated C Data Interface structure that was then passed to Go. The solution was to have the Go callback pass through a trampoline to zero structures before Go could "see" them. This looks like it's going to be a similar kind of issue but not quite the same. If there's some way to reproduce it somewhat reliably, it could be instructive to run it under `rr` (or similar debugger) and back up to figure out what happened... -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
