Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 24 Aug 2017 15:09:47 +0200
From: Pirmin Walthert <>
Subject: Re: gethostbyname2.c /
 6476b8135760659b25c93ff9308425ca98a9e777 breaking asterisk 13 compatibility

Hi Timo

Thanks, we use Asterisk 13 since months on about 100 VM's with musl, we
have only one strange issue that leads to a crashes from time to time,
especially when using PickupChan. Somehow I couldn't reproduce the
crash when using only hostnames in FROM headers that I'd put into
/etc/hosts (but as it is hard to reproduce anyway it's not sure whether
this is really the reason). However I've seen that some pjsip functions
used in the multihomed module (in asterisk 13 at least) are using
gethostbyname (not gethostbyname_r). 

I'm waiting for feedback from the asterisk team whether it's possible
that several threads are using the multihomed code at the same time.

Asterisk 14 has some changes in the resolver, so maybe that's the
reason why Asterisk 14 isn't affected.

Best regards,


Am Donnerstag, den 24.08.2017, 15:58 +0300 schrieb Timo Teras:
> On Thu, 24 Aug 2017 13:39:08 +0200
> Pirmin Walthert <> wrote:
> > First thing:
> >
> > 659b25c93ff9308425ca98a9e777 seems to break Asterisk compatibilty.
> > Asterisk crashes on every startup while loading modules. Using
> > musl-git combined with the latest dynlink.c version before this
> > commit works fine. (1.1.16 has some startup crashes as well because
> > of the bug fixed with 27b3fd68f67b674440d21ea7ca5cf918d2e1559f).
> I am using asterisk 14 just fine on Alpine linux with current musl
> git
> master. We needed few patches though. Maybe those help you too:
> Though, some issues might be relevant to specific modules.
> Timo

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.