[x264-devel] --enable-pic with 8x8dct produces illegal instruction
İsmail Dönmez
ismail at pardus.org.tr
Mon Sep 11 13:04:36 CEST 2006
Hi,
When --enable-pic is used in conjuction with 8x8dct x264 produces an illegal
instruction:
x264 -8 2.mpeg -o 2.mp4 640x480
x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2
mp4 [info]: initial delay 0 (scale 25)
Segmentation fault
Valgrind says:
vex x86->IR: unhandled instruction bytes: 0xFB 0x12 0x8 0xF0
==22795== valgrind: Unrecognised instruction at address 0x812FE85.
==22795== Your program just tried to execute an instruction that Valgrind
==22795== did not recognise. There are two possible reasons for this.
==22795== 1. Your program has a bug and erroneously jumped to a non-code
==22795== location. If you are running Memcheck and you just saw a
==22795== warning about a bad jump, it's probably your program's fault.
==22795== 2. The instruction is legitimate but Valgrind doesn't handle it,
==22795== i.e. it's Valgrind's fault. If you think this is the case or
==22795== you are not sure, please let us know and we'll try to fix it.
==22795== Either way, Valgrind will now raise a SIGILL signal which will
==22795== probably kill your program.
==22795==
==22795== Process terminating with default action of signal 4 (SIGILL)
==22795== Illegal opcode at address 0x812FE85
==22795== at 0x812FE85: ???
==22795== by 0x8087123: x264_macroblock_analyse (analyse.c:1979)
==22795== by 0x8055D7E: x264_slice_write (encoder.c:1006)
==22795== by 0x8056D1B: x264_encoder_encode (encoder.c:1127)
==22795== by 0x804CBEA: Encode_frame (x264.c:686)
==22795== by 0x804CEB9: Encode (x264.c:772)
==22795== by 0x804B8CB: main (x264.c:110)
All mpeg files shows the same problem, x264 is from SVN.
Regards,
ismail
--
アニメは本当にすごいすぎるよ !
--
This is the x264-devel mailing-list
To unsubscribe, go to: http://developers.videolan.org/lists.html
More information about the x264-devel
mailing list