You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/06/29 23:44:00 UTC
[jira] [Commented] (DISPATCH-1678) Enable alloc_pool leak checker
in travis
[ https://issues.apache.org/jira/browse/DISPATCH-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148214#comment-17148214 ]
ASF GitHub Bot commented on DISPATCH-1678:
------------------------------------------
kgiusti opened a new pull request #769:
URL: https://github.com/apache/qpid-dispatch/pull/769
This patch updates the alloc_pool.c debug code to free any "leaked"
items to prevent ASAN from printing tracebacks for them. These
tracebacks are misleading since ASAN only tracks the initial heap
malloc, not the last time the item was allocated from the pool.
Add a list of alloc_pool.c types that are known/expected to leak. If
the alloc_pool.c debug code finds a leak for a type which is NOT on
this list the router will abort on shutdown (debug build only).
Update the .travis.yml to clean up warnings and include a test run of
the default build case.
Update the LSAN suppression file.
Improve dumping of logs on router crash.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> Enable alloc_pool leak checker in travis
> ----------------------------------------
>
> Key: DISPATCH-1678
> URL: https://issues.apache.org/jira/browse/DISPATCH-1678
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
> Affects Versions: 1.12.0
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Priority: Major
> Fix For: 1.13.0
>
>
> Travis currently uses ASAN for leak detection.
> This tool does identify leaks, but it only tracks the initial allocation of the object from the heap.
> This trace information can be inaccurate for objects stored in alloc pools, since it does not account for when objects are returned by to the pool.
> By enabling the built-in alloc_pool leak checker as well we'll get more accurate traces that identify the last owner of the leaked object.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org