[
https://issues.apache.org/jira/browse/DISPATCH-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351070#comment-14351070
]
ASF subversion and git services commented on DISPATCH-121:
----------------------------------------------------------
Commit 1664744 from [~aconway] in branch 'dispatch/trunk'
[ https://svn.apache.org/r1664744 ]
DISPATCH-121: Allow memory pools to be switched off at compile time.
For debugging purposes to get better results from toolsl like valgrind.
Fixed memory bugs
- Numerous memory bugs in tests.
- Invalid read in qd_hash_free (remove from DEQ after free)
- Added missing qd_timer_finalize in qd_server_free
> Allow pool allocation to be switched for plain allocation at build time.
> ------------------------------------------------------------------------
>
> Key: DISPATCH-121
> URL: https://issues.apache.org/jira/browse/DISPATCH-121
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Affects Versions: 0.3
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 0.5
>
> Attachments: disable_pools.diff
>
>
> Memory checking tools like valgrind can't give much help when we use a custom
> allocator.
> Make it possible to build dispatch using malloc/free instead so it can be
> checked with valgrind.
> This is not the ideal solution. It tests the code that uses the allocator but
> does not test the allocator itself.
> A better solution is to instrument the allocator for valgrind use, see:
> http://www.valgrind.org/docs/manual/mc-manual.html#mc-manual.mempools
> However this is more complex and doesn't help with other memory debugging
> tools. Disabling pools at build time is a useful first step. It also lets us
> test performance of the pool allocator against plain malloc. A full valgrind
> integration with pool allocation is a possible future exercise.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
