[ARROW-13042] [C++] Automatic checks that kernels don't leave uninitialized data in output

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.0.0
• Component/s: C++
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/28753
• Assignee: Antoine Pitrou
• Reporter: Antoine Pitrou
• Created: 10/Jun/21 20:28
• Updated: 11/Jan/23 08:30
• Resolved: 21/Jun/21 12:04

Description

To minimize the risk of issues such as ARROW-13041, perhaps our compute kernel test harness should include a check that allocated data is always initialized (using Valgrind).

Issue Links

• is related to: ARROW-13041 [C++] Unary kernels can leave uninitialized data under null entries
• links to: GitHub Pull Request #10550