[
https://issues.apache.org/jira/browse/DISPATCH-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148740#comment-17148740
]
ASF subversion and git services commented on DISPATCH-1678:
-----------------------------------------------------------
Commit b92a885a2261170abd118d670cc0fc4710741cef in qpid-dispatch's branch
refs/heads/master from Ken Giusti
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=b92a885 ]
DISPATCH-1678: fix misleading ASAN tracebacks for pooled items
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.
This closes #769
> 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: [email protected]
For additional commands, e-mail: [email protected]
