Source: yorick-av Version: 0.0.1-2 Severity: serious Tags: sid jessie yorick-av FTBFS on amd64: | ========================================== | testing extension: 'mkv' | ========================================== | Output #0, matroska, to 'libavcheck.mkv': | Stream #0.0: Video: libx264, yuv420p, 704x288, q=-1--1, 400 kb/s, 90k tbn, 24 tbc | [libx264 @ 0x170e260] using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2 AVX | [libx264 @ 0x170e260] profile High, level 2.1 | [libx264 @ 0x170e260] 264 - core 123 r2189 35cf912 - H.264/MPEG-4 AVC codec - Copyleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=16 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=25 keyint_min=2 scenecut=40 intra_refresh=0 rc_lookahead=25 rc=abr mbtree=1 bitrate=400 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.25 aq=1:1.00 | ERROR (*main*) Floating point interrupt (SIGFPE) | make[1]: *** [check-dll] Segmentation fault (core dumped) | make[1]: Leaving directory `/«PKGBUILDDIR»' | dh_auto_test: make -j1 check returned exit code 2
The full build log is available at http://people.debian.org/~sramacher/logs/yorick-av_0.0.1-2_amd64-20130826-2058.log Please note that on another amd64 machine, the test runs through successfully: | ========================================== | testing extension: 'mkv' | ========================================== | Output #0, matroska, to 'libavcheck.mkv': | Stream #0.0: Video: libx264, yuv420p, 704x288, q=-1--1, 400 kb/s, 90k tbn, 24 tbc | [libx264 @ 0x1581aa0] using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64 | [libx264 @ 0x1581aa0] profile High, level 2.1 | [libx264 @ 0x1581aa0] 264 - core 123 r2189 35cf912 - H.264/MPEG-4 AVC codec - Copyleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 d | eblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 c | hroma_qp_offset=-2 threads=6 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=16 b_pyramid=2 b_adapt=1 b_bias=0 direct | =1 weightb=1 open_gop=0 weightp=2 keyint=25 keyint_min=2 scenecut=40 intra_refresh=0 rc_lookahead=25 rc=abr mbtree=1 bitrate=400 ratetol=1.0 qcomp=0.60 qpmin=0 | qpmax=69 qpstep=4 ip_ratio=1.25 aq=1:1.00 | done, closing file 'libavcheck.mkv' The difference seems to be the CPU capabilities selected by libx264. And indeed, the SIGFPE happens in libx264.so.123: (gdb) bt #0 0x00007ffff43e1944 in ?? () from /usr/lib/x86_64-linux-gnu/libx264.so.123 #1 0x00007ffff436f127 in ?? () from /usr/lib/x86_64-linux-gnu/libx264.so.123 #2 0x00007ffff4371ae8 in ?? () from /usr/lib/x86_64-linux-gnu/libx264.so.123 #3 0x00007ffff4391b78 in x264_slicetype_analyse () from /usr/lib/x86_64-linux-gnu/libx264.so.123 #4 0x00007ffff43d387d in ?? () from /usr/lib/x86_64-linux-gnu/libx264.so.123 #5 0x00007ffff43d3979 in ?? () from /usr/lib/x86_64-linux-gnu/libx264.so.123 #6 0x00007ffff49d0e0e in start_thread (arg=0x7fffedf57700) at pthread_create.c:311 #7 0x00007ffff72da93d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 X-Debbugs-CC-ing the libx264 maintainers in the hope they might know something about this. Regards -- Sebastian Ramacher
signature.asc
Description: Digital signature