[
https://issues.apache.org/jira/browse/ARROW-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721524#comment-16721524
]
Wes McKinney commented on ARROW-4009:
-------------------------------------
I agree that valgrind does provide useful insights. It can find things (like
memory leaks) that that ASAN does not. It requires an up to date clang indeed
Lucky because the way we manage memory, leaks in the C++ are rare which has
been nice
> [CI] Run Valgrind and C++ code coverage in different bulds
> ----------------------------------------------------------
>
> Key: ARROW-4009
> URL: https://issues.apache.org/jira/browse/ARROW-4009
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, Continuous Integration
> Affects Versions: 0.11.1
> Reporter: Antoine Pitrou
> Priority: Major
>
> Currently, we run Valgrind on a coverage-enabled C++ build on Travis-CI. This
> means the slowness of Valgrind acts as a multiplier of the overhead of
> outputting coverage information using the instrumentation added by the
> compiler.
> Instead we should probably emit C++ (and Python) coverage information in a
> different Travis-CI build without Valgrind enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
