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

Jason Garrett-Glaser darkshikari at gmail.com
Wed Mar 4 04:21:44 CET 2009


2009/3/3 191919 <191919 at gmail.com>:
> ==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.

Well, you know, except for the part where they are?

#define DIA1_ITER( mx, my )\
{\
    omx = mx; omy = my;\
    COST_MV_X4( 0,-1, 0,1, -1,0, 1,0 );\
}

Dark Shikari


More information about the x264-devel mailing list