[
https://issues.apache.org/jira/browse/MINIFI-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994996#comment-15994996
]
marco polo commented on MINIFI-191:
-----------------------------------
[~achristianson] Agreed. We could launch this within travis too.
http://stackoverflow.com/questions/40325957/how-do-i-add-valgrind-tests-to-my-cmake-test-target
is but one example. I've used one at a job that did things a bit differently,
but don't have access to that CMakeLists.txt file. I'll update the title.
> Run valgrind on minifi-cpp
> --------------------------
>
> Key: MINIFI-191
> URL: https://issues.apache.org/jira/browse/MINIFI-191
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: C++
> Affects Versions: cpp-0.1.0
> Reporter: marco polo
> Assignee: marco polo
>
> I've been able to expose paths for at lest one memory leak. I want to run
> valgrind to check as many paths as possible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
