[asterisk-bugs] [JIRA] Feedback Entered: (ASTERISK-19971) Segfault in realtime_multi_ldap (possible invalid arguments)

Lars Peter Thomsen (JIRA) noreply at issues.asterisk.org
Wed Jul 25 07:20:21 CDT 2012


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

Lars Peter Thomsen updated ASTERISK-19971:
------------------------------------------

    Send back to Developer?: I'm not done! I will comment again later to send it back.  (was: I'm done. Send it back!)
                     Status: Waiting for Feedback  (was: Waiting for Feedback)

I solved the issue by updating the config files, thus sidestepping the segfault. Now I'm trying to recreate the situation where the segfault occurs. It may take a while, as other issues get in the way. I'll update the bug when I have more.

> Segfault in realtime_multi_ldap (possible invalid arguments)
> ------------------------------------------------------------
>
>                 Key: ASTERISK-19971
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19971
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.11.1
>         Environment: Ubuntu 10.04 64-bit
>            Reporter: Lars Peter Thomsen
>            Assignee: Lars Peter Thomsen
>         Attachments: debug_asterisk_gdb2.txt, debug_asterisk_gdb.txt, debug_asterisk_valgrind.txt
>
>
> Realtime LDAP module kills asterisk with a segfault when querying for extensions. It appears to happen in the realtime_multi_ldap function in res_config_ldap.c, where the newparam variable somehow is invalid (null or garbage). The warning in checking the variable is fired in several runs prior to the fault.
> Calls go through every time before the fault, with the aforementioned warning being fired each time, and on the 8th to 10th attempt, the segfault occurs.
> Disabling realtime extensions in extconfig.conf, so only users, peers and voicemail data is fetched from LDAP, while extensions are fetched from extensions.conf, causes the problem to not occur.
> Entry in extconfig.conf:
> extensions => ldap,"ou=extensions,dc=communica,dc=cabo,dc=dk",extensions
> Entry in res_ldap.conf:
>  ; Extensions Table
>  [extensions]
>  context = AstContext
>  exten = AstExtension
>  priority = AstPriority
>  app = AstApplication
>  appdata = AstApplicationData
>  additionalFilter=(objectClass=AsteriskExtension)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list