[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1503574813.12219.17.camel@wwcom.ch>
Date: Thu, 24 Aug 2017 13:40:13 +0200
From: Pirmin Walthert <pirmin.walthert@...om.ch>
To: musl@...ts.openwall.com
Subject: Re: gethostbyname2.c /
6476b8135760659b25c93ff9308425ca98a9e777 breaking asterisk 13 compatibility
(has not been initialized)
Am Donnerstag, den 24.08.2017, 13:39 +0200 schrieb Pirmin Walthert:
> Hello
>
> First thing: http://git.musl-libc.org/cgit/musl/commit/?id=6476b81357
> 60
> 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).
>
> Second: I'm currently debugging a strange memory corruption problem
> and
> have just had a look at the gethostbyname2.c code:
>
> I was wondering: why is it safe to do free(h) on the initial run when
> *h has not been
>
> static struct hostent *h;
> size_t size = 63;
> struct hostent *res;
> int err;
> do {
> free(h);
>
> Best regards,
>
> Pirmin
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.
