[asterisk-bugs] [JIRA] (ASTERISK-15719) glibc 2.11.1 causes asterisk to not start due to return code from dlclose

[Matt Jordan (JIRA)]

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

Matt Jordan closed ASTERISK-15719.
----------------------------------

    Resolution: Fixed

This was fixed in r402287 in 1.8+.

> glibc 2.11.1 causes asterisk to not start due to return code from dlclose
> -------------------------------------------------------------------------
>
>                 Key: ASTERISK-15719
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-15719
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Core/General
>            Reporter: Quentin Armitage
>            Severity: Minor
>
> On Fedora-12, with its current glibc (glibc-2.11.1-1), asterisk fails to start up when it loads any module.
> In main/loader.c there are 4 instances of the following code:
>      while (!dlclose(lib));
> dlclose() in glibc-2.11.1-1 returns 0 (SUCCESS) even if the library has already been closed, and consequently the while loop never terminates.
> On Fedora-11 (with glibc-2.10.2-1) and Fedora-13 (with glibc-2-11-90.14), dlclose() returns -1 if the library is already closed, and so the problem does not occur.
> This issue certain occurs with asterisk version 1.6.1.12 and later (including current SVN head).
> ****** ADDITIONAL INFORMATION ******
> I reported this as a bug in glibc (see https://bugzilla.redhat.com/show_bug.cgi?id=569060 ), and the response was that this is undefined behaviour.
> I have reported the problem against Asterisk in Fedora, (see https://bugzilla.redhat.com/show_bug.cgi?id=569384 ), and have been asked to report it upstream. There is an ugly patch attached to that bug report as a workaround to the problem.



--
This message was sent by Atlassian JIRA
(v6.2#6252)