[jira] [Updated] (DISPATCH-121) Allow pool allocation to be switched for plain allocation at build time.

["Alan Conway (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DISPATCH-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Conway updated DISPATCH-121:
---------------------------------
    Summary: Allow pool allocation to be switched for plain allocation at build time.  (was: Alllow pool allocation to be switched for plain allocation at build time.)

> 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