[x264-devel] Some valgrind warnings on uninitialized variables in me.c

[Alexander Strange]

On Mar 3, 2009, at 10:04 PM, 191919 wrote:

> ==493== Conditional jump or move depends on uninitialised value(s)
> ==493==    at 0x47AA07: x264_me_search_ref (in /usr/local/bin/ffmpeg)
> ==493==
> ==493== Conditional jump or move depends on uninitialised value(s)
> ==493==    at 0x47B3E1: x264_me_search_ref (in /usr/local/bin/ffmpeg)
>
>  164     int omx, omy, pmx, pmy;
> ...
>  239             if( (bmx == omx) & (bmy == omy) )
>  240                 break;
>
> omx and omy are not initialized.
>
> Regards,
> jh

Since you're using OS X valgrind, you have the --track-origins=yes  
option. Use it; it's the only way to make uninitialized value warnings  
helpful.
Also run the trace against x264 (with debugging enabled) or ffmpeg_g.