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 subversion and git services (JIRA)" <ji...@apache.org> on 2015/03/06 23:45:38 UTC
[jira] [Commented] (DISPATCH-121) Allow pool allocation to be
switched for plain allocation at build time.
[ https://issues.apache.org/jira/browse/DISPATCH-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351062#comment-14351062 ]
ASF subversion and git services commented on DISPATCH-121:
----------------------------------------------------------
Commit 1664743 from [~aconway] in branch 'dispatch/trunk'
[ https://svn.apache.org/r1664743 ]
DISPATCH-121: Workaround to force cmake re-configure.
reconfigure.in is a workaround to force cmake re-configuration. For example,
we use GLOB to collect .h files for install and apidoc, so if you _remove_ a
.h file it won't trigger automatic re-configure and everybody's builds will
fail till they run cmake manually.
If you do check in such a change, increase the number in this file by 1.
That will force automatic re-configure and everybody will be happy.
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org