[
https://issues.apache.org/jira/browse/ARROW-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839103#comment-16839103
]
Pindikura Ravindra commented on ARROW-5270:
-------------------------------------------
There are two issues :
# instructions not recognized by valgrind
=20276== Your program just tried to execute an instruction that Valgrind
==20276== did not recognise. There are two possible reasons for this. ==20276==
1. Your program has a bug and erroneously jumped to a non-code ==20276==
location. If you are running Memcheck and you just saw a ==20276== warning
about a bad jump, it's probably your program's fault.
2. the re2 issues
I think these are already covered by the suppressions listed in the
valgrind.supp but they aren't being recognized due to missing symbols in the
stack.
When I ran this on my xenial setup without any conda setup, the stacks showed
up correctly and got suppressed. so, I suspect this is an issue with conda
binaries.
> [C++] Reenable Valgrind on Travis-CI
> ------------------------------------
>
> Key: ARROW-5270
> URL: https://issues.apache.org/jira/browse/ARROW-5270
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, Continuous Integration
> Reporter: Antoine Pitrou
> Priority: Critical
> Labels: pull-request-available
> Fix For: 0.14.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Running Valgrind on Travis-CI was disabled in ARROW-4611 (apparently because
> of issues within the re2 library).
> We should reenable it at some point in order to exercise the reliability of
> our C++ code.
> (and/or have a build with another piece of instrumentation enabled such as
> ASAN)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
