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 2017/08/23 02:14:01 UTC

[jira] [Created] (ARROW-1401) [C++] Add extra debugging context to failures in RETURN_NOT_OK in debug builds

Wes McKinney created ARROW-1401:
-----------------------------------

             Summary: [C++] Add extra debugging context to failures in RETURN_NOT_OK in debug builds
                 Key: ARROW-1401
                 URL: https://issues.apache.org/jira/browse/ARROW-1401
             Project: Apache Arrow
          Issue Type: Improvement
          Components: C++
            Reporter: Wes McKinney
             Fix For: 0.7.0


This should show

* the statement that failed
* the file and line number

I implemented this for CUDA failures in https://github.com/apache/arrow/pull/985 and I really like it. If we add glog to our toolchain we may be able to get full stack traces on failures. 

It would probably increase code size to much in release builds, so it should be a DEBUG only feature. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)