[asterisk-bugs] [JIRA] (ASTERISK-22536) MALLOC_DEBUG causes /tmp/refs to be written, even if REF_DEBUG is not defined

Matt Jordan (JIRA) noreply at issues.asterisk.org
Mon Oct 21 12:58:19 CDT 2013


     [ https://issues.asterisk.org/jira/browse/ASTERISK-22536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-22536:
-----------------------------------

    Target Release Version/s: 11.6.0
    
> MALLOC_DEBUG causes /tmp/refs to be written, even if REF_DEBUG is not defined
> -----------------------------------------------------------------------------
>
>                 Key: ASTERISK-22536
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22536
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General
>    Affects Versions: 1.8.23.1, 11.5.1, 12.0.0-alpha1
>            Reporter: David M. Lee
>            Assignee: David M. Lee
>      Target Release: 1.8.24.0, 11.6.0
>
>
> When MALLOC_DEBUG is defined, Asterisk writes out the {{/tmp/refs}} file, even if {{REF_DEBUG}} is not set. The only items written to {{/tmp/refs}} are related to {{container_destruct_debug}}.
> {code}
> 0xa113c6c -1   astobj2.c:1731:container_destruct_debug (container_destruct_debug called) [@1]
> 0xa6cb124 -1   astobj2.c:1731:container_destruct_debug (container_destruct_debug called) [@1]
> 0xa62adb4 -1   astobj2.c:1731:container_destruct_debug (container_destruct_debug called) [@1]
> 0xa62b2f4 -1   astobj2.c:1731:container_destruct_debug (container_destruct_debug called) [@1]
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list