[asterisk-bugs] [JIRA] (ASTERISK-17386) [patch] res_config_ldap with malloc_debug produces munmap_chunk(): invalid pointer:

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-17386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205109#comment-205109 ] 

Matt Jordan edited comment on ASTERISK-17386 at 4/9/13 3:30 PM:
----------------------------------------------------------------

If this worked on trunk, I feel reasonably confident that it will work with 1.8/11, as the code in res_config_ldap has changed very little between the various branches.

If you're okay with it going in, I don't mind committing it.
                
      was (Author: mjordan):
    If this worked on trunk, I feel reasonably confident that it will work with 1.8/11, as the code in res_config_ldap has changed very little between the various branches.

If you're okay with it going on, I don't mind committing it.
                  
> [patch] res_config_ldap with malloc_debug produces munmap_chunk(): invalid pointer:
> -----------------------------------------------------------------------------------
>
>                 Key: ASTERISK-17386
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17386
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Resources/res_config_ldap
>    Affects Versions: 1.8.2
>            Reporter: John Covert
>            Assignee: Andrew Latham
>            Severity: Critical
>         Attachments: ASTERISK-17386-1.8.diff, backtrace.txt, issue18789-1.8-r316873.patch
>
>
> If malloc_debug is turned on, as soon as an ldap realtime peer attempts to register, wham.
> This occurs at the ldap_mods_free call at line 1338.
> Problem occurs with or without the patch from issue 18435 (i.e. with straight 1.8.2.3 or with SVN revision 304866 of res_config_ldap.c)
> Runs "ok" without malloc_debug.
> Backtrace attached.

--
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