[
https://issues.apache.org/jira/browse/ARROW-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16734377#comment-16734377
]
Wes McKinney commented on ARROW-4150:
-------------------------------------
I renamed the issue to make it a bit more explicit what is going on
> [C++] Do not return buffers containing nullptr from internal allocations
> ------------------------------------------------------------------------
>
> Key: ARROW-4150
> URL: https://issues.apache.org/jira/browse/ARROW-4150
> Project: Apache Arrow
> Issue Type: Wish
> Components: C++
> Affects Versions: 0.11.1
> Reporter: Antoine Pitrou
> Assignee: Antoine Pitrou
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.12.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When a 0-byte buffer is allocated, or at the start of a BufferBuilder, the
> buffer's data pointer can be null. This leads to passing null arguments (with
> zero sizes) to standard functions such as memset() and memcpy() in many
> places. UBSAN doesn't like it.
> Since a null pointer often means "failed allocating" or "programmer error",
> we might want to use a non-null pointer to a static empty piece of data
> instead.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
