You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@arrow.apache.org by "Antoine Pitrou (JIRA)" <ji...@apache.org> on 2019/01/03 15:34:00 UTC

[jira] [Created] (ARROW-4150) [C++] Buffer data should never be null

Antoine Pitrou created ARROW-4150:
-------------------------------------

             Summary: [C++] Buffer data should never be null
                 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


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)