[test-results] [Bamboo] Asterisk > Asterisk Build > #1854 was SUCCESSFUL. Change made by Joshua Colp.

[Bamboo]

-----------------------------------------------------------------------
Asterisk > Asterisk Build > #1854 was successful.
-----------------------------------------------------------------------
Code has been updated by Joshua Colp.
All 2 jobs passed

https://bamboo.asterisk.org/bamboo/browse/AST-ATRUNKBUILD-1854/




--------------
Code Changes
--------------
Joshua Colp (e092a896947e28ab43d375199d6d6c792a210bb9):

>Merge "MALLOC_DEBUG: Replace WRAP_LIBC_MALLOC with ASTMM_LIBC."

Corey Farrell (478fb4a388afcb56e7e50184c996f0838d609a66):

>MALLOC_DEBUG: Replace WRAP_LIBC_MALLOC with ASTMM_LIBC.
>There are 3 ways that calls directly to standard allocator functions can
>be dealt with:
>1. Block their use, cause them to generate an error.  This is the default.
>2. Replace them with the Asterisk equivalent function calls.
>3. Leave them alone.
>
>This change allows one of these 3 options to be selected by any source.
>The source just needs to define ASTMM_LIBC to ASTMM_BLOCK, ASTMM_REDIRECT,
>or ASTMM_IGNORE to use option 1, 2 or 3 respectively.  Normally ASTMM_BLOCK
>is the correct option, so it is default when ASTMM_LIBC is not defined.
>In some cases when building 3rd party code it is desirable to have it use
>Asterisk functions, without changing the whole source - ASTMM_REDIRECT
>accomplishes this.  When using 3rd party libraries sometimes a static
>inline function will make use of malloc or free.  In these cases it may
>be unsafe to replace the allocator in the header, as it's possible the
>memory could be freed by the library using standard allocators.  For
>those cases ASTMM_IGNORE is needed.
>
>Change-Id: I8afef4bc7f3b93914263ae27d3a5858b69663fc7



--
This message is automatically generated by Atlassian Bamboo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/test-results/attachments/20150514/49edfefc/attachment-0001.html>