[x264-devel] x264 svn HEAD SIGSEGV

Guillaume Poirier gpoirier at mplayerhq.hu
Sun Mar 2 18:25:29 CET 2008


Hello,

Gunter Ohrner wrote:
> Hi!
> 
> Trying to encode a video, I consistently run into the following crash:
> 
> Program terminated with signal 11, Segmentation fault.
> #0  0xb7f0d266 in x264_pixel_satd_8x8_sse2 () from /usr/lib/libx264.so.58
> (gdb) bt
> #0  0xb7f0d266 in x264_pixel_satd_8x8_sse2 () from /usr/lib/libx264.so.58
> #1  0xb7ebef5e in x264_slicetype_mb_cost () from /usr/lib/libx264.so.58
> #2  0xb7ebf248 in x264_slicetype_frame_cost () from /usr/lib/libx264.so.58
> #3  0xb7ec0c81 in x264_rc_analyse_slice () from /usr/lib/libx264.so.58
> #4  0xb7ede286 in ?? () from /usr/lib/libx264.so.58
> 
> This happened with both r736 (from the debian multimedia repository) and
> r745 (custom-compiled), machine is an Core 2 Duo T7200. libx264 was driven
> by mencoder 1.0rc2 svn from december (recompiled against the current
> libx264, of course) which works fine with older libx264s (r714 from the
> debian multimedia repository, in paticular). Compiler was Debian's gcc
> 4.2.3.
> 
> Do you need any further information? I could recompile with debugging
> symbols enabled if neccessary.

Well, backtraces are much more useful when they are produced with a
binary compiled with debug symbols. Also, please provide a disass of
the offending code, as well as a dump of registers.
There's a nice summary of what's useful here:
http://www.mplayerhq.hu/DOCS/HTML/en/bugreports_what.html#bugreports_crash

Guillaume


More information about the x264-devel mailing list