You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2018/03/09 15:25:00 UTC
[jira] [Resolved] (ARROW-2275) [C++] Buffer::mutable_data_ member
uninitialized
[ https://issues.apache.org/jira/browse/ARROW-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wes McKinney resolved ARROW-2275.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.9.0
Issue resolved by pull request 1717
[https://github.com/apache/arrow/pull/1717]
> [C++] Buffer::mutable_data_ member uninitialized
> ------------------------------------------------
>
> Key: ARROW-2275
> URL: https://issues.apache.org/jira/browse/ARROW-2275
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
> Affects Versions: 0.8.0
> Reporter: Antoine Pitrou
> Priority: Minor
> Labels: pull-request-available
> Fix For: 0.9.0
>
>
> For immutable buffers (i.e. most of them), the {{mutable_data_}} member is uninitialized. If the user calls {{mutable_data()}} by mistake on such a buffer, they will get a bogus pointer back.
> This is exacerbated by the Tensor API whose const and non-const {{raw_data()}} methods return different things...
> (also an idea: add a DCHECK for mutability before returning from {{mutable_data()}}?)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)