Re: [asterisk-dev] (unreported) uninitialized: struct ast_sockaddr

2015-05-13 Thread Richard Mudgett
On Wed, May 13, 2015 at 3:59 AM, Alexander Traud pabstr...@compuserve.com wrote: What you're proposing is a change to the semantics of ast_sockaddr. Not sure what you mean by semantics. Please, let us ignore ast_sockaddr for a second and see

Re: [asterisk-dev] (unreported) uninitialized: struct ast_sockaddr

2015-05-12 Thread Matthew Jordan
On Mon, May 11, 2015 at 9:16 AM, Alexander Traud pabstr...@compuserve.com wrote: B) Change my patch not to use a char* but char[128]. Your easiest option with less chance of regression elsewhere would be this. Yes. Anyway: Is the Asterisk team interested in a patch at least for the 5 affected

Re: [asterisk-dev] (unreported) uninitialized: struct ast_sockaddr

2015-05-11 Thread Joshua Colp
Alexander Traud wrote: In a patch of mine (DANE for Asterisk 13/chan_sip; available on request), a char* was added in the struct ast_sockaddr to store the DNSSEC failure reason (why_bogus). Not to create any memory leaks, this pointer has to be freed. For this, the pointer must be initialized to

Re: [asterisk-dev] (unreported) uninitialized: struct ast_sockaddr

2015-05-11 Thread Alexander Traud
B) Change my patch not to use a char* but char[128]. Your easiest option with less chance of regression elsewhere would be this. Yes. Anyway: Is the Asterisk team interested in a patch at least for the 5 affected files? These are 54 changes. I am not sure if the path via an issue (Jira) and a