[GitHub] [arrow] hermanschaaf opened a new issue, #35234: [Go] Two additional frames need to be skipped in Checked Allocator output

["hermanschaaf (via GitHub)" <gi...@apache.org>]

hermanschaaf opened a new issue, #35234:
URL: https://github.com/apache/arrow/issues/35234

   ### Describe the bug, including details regarding any error messages, version, and platform.
   
   When ARROW_CHECKED_MAX_RETAINED_FRAMES is set to a value greater than zero, the frames currently printed include the frame below the caller and the caller itself, which means the caller is listed twice. We should skip 2 additional frames in the `Callers` code as done in https://github.com/apache/arrow/pull/35231
   
   ### Component(s)
   
   Go


-- 
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: issues-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [arrow] zeroshade closed issue #35234: [Go] Two additional frames need to be skipped in Checked Allocator output

["zeroshade (via GitHub)" <gi...@apache.org>]

zeroshade closed issue #35234: [Go] Two additional frames need to be skipped in Checked Allocator output
URL: https://github.com/apache/arrow/issues/35234


-- 
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: issues-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org