[Freeswitch-users] mod_spandsp compile error

[Steve Underwood]

You are probably right, but the only thing I see which might be 
non-compliant (although I don't think it is) is that in two places 
memcpy can be called with a bad pointer when the length is zero. I just 
changed the code so memcpy is only called when the length is non-zero. 
Let's see what happens with that.

Regards,
Steve

On 10/17/2013 08:21 PM, Steven Ayre wrote:
> I'm guessing the warning is because decode_open_type gets a pointer to 
> them before they're initialised. Not a problem if they're only for 
> output but guessing the compiler can't tell that.
>
>
> On 17 October 2013 13:00, Steve Underwood <steveu at coppice.org 
> <mailto:steveu at coppice.org>> wrote:
>
>     On 10/17/2013 07:13 AM, Sadjad Seyed-Ahmadian wrote:
>     > Hi,
>     >
>     > I am try to install a FreeSWITCH stable version 1.2.13 on a fresh
>     > CentOS. I installed all prereqired packages as they are in wiki,
>     > configure goes well but while I try to do make I got this error on
>     > mod_spandsp.
>     >
>     >
>     > making all mod_spandsp
>     > Creating mod_spandsp_la-mod_spandsp.lo
>     > mkdir .libs
>     > Compiling mod_spandsp.c ...
>     > Creating mod_spandsp_la-udptl.lo
>     > Compiling udptl.c ...
>     > cc1: warnings being treated as errors
>     > udptl.c: In function 'udptl_rx_packet':
>     > udptl.c:174: warning: 'data' may be used uninitialized in this
>     function
>     > udptl.c:173: warning: 'msg' may be used uninitialized in this
>     function
>     > make[3]: *** [mod_spandsp_la-udptl.lo] Error 1
>     > make[2]: *** [mod_spandsp-all] Error 1
>     > make[1]: *** [mod_spandsp] Error 2
>     > make: *** [mod_spandsp] Error 2
>     >
>     >
>     > Would somebody please help me with that?
>     >
>     > Best Regards
>     > Sadjad
>     >
>     Centos 6.4 doesn't do that. Which version of Centos are you using? I
>     might be missing something, but those two warnings seem bogus.
>
>     Steve
>