You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <ji...@apache.org> on 2017/11/16 21:27:00 UTC
[jira] [Commented] (DISPATCH-739) Enable valgrind leak-check=full
and fix any memory errors found
[ https://issues.apache.org/jira/browse/DISPATCH-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255994#comment-16255994 ]
Alan Conway commented on DISPATCH-739:
--------------------------------------
I'm out of the loop on dispatch so not sure if it is valgrind-clean yet or not - if it is please resolve this issue
> Enable valgrind leak-check=full and fix any memory errors found
> ---------------------------------------------------------------
>
> Key: DISPATCH-739
> URL: https://issues.apache.org/jira/browse/DISPATCH-739
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
> Affects Versions: 0.7.0
> Reporter: Alan Conway
> Assignee: Ganesh Murthy
>
> Enable valgrind --leak-check=full with --show-leak-kinds=definite to avoid flood of "possibly lost" false alarms from python. Fix any memory errors this reveals.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org