[Ffmpeg-devel] Illegal instruction error for ffmpeg and x264 on Intel iMac
Fri Mar 31 22:03:46 CEST 2006
On 3/31/06, Laine Lee <llee at lonestar.utsa.edu> wrote:
> On 3/31/06 1:29 PM, "Guillaume POIRIER" <poirierg at gmail.com> wrote:
> > Hi,
> > On 3/31/06, Laine Lee <llee at lonestar.utsa.edu> wrote:
> >> The only difference I see when I run with debugging enabled is that "Program
> >> exited with code 0204." appears instead of "Illegal instruction".
> > you need to provide a back trace and a dis-assembly of the part of
> > code where the error occurred (the link I gave you explains that I
> > believe).
> > Guillaume
> Thank you for guiding me.
> Here's what I have.
> (gdb) r -i /video.mpg -f rawvideo -s 320x240 -|/usr/local/bin/x264 -o
> /output.mp4 - 320x240
> Starting program: /Users/me/ffmpeg/ffmpeg_g -i /video.mpg -f rawvideo -s
> 320x240 -|/usr/local/bin/x264 -o /output.mp4 - 320x240
> x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2
> mp4 [info]: initial delay 0 (scale 25)
> FFmpeg version CVS, Copyright (c) 2000-2004 Fabrice Bellard
> configuration: --enable-faac --enable-faad --disable-vhook
> --disable-ffplay --disable-ffserver --enable-a52 --enable-x264
> --enable-pthreads --enable-gpl --enable-memalign-hack --disable-mmx
> libavutil version: 49.0.0
> libavcodec version: 51.8.0
> libavformat version: 50.4.0
> built on Mar 31 2006 12:29:38, gcc: 4.0.1 (Apple Computer, Inc. build
> Input #0, mpeg, from '/video.mpg':
> Duration: 00:00:26.4, start: 5810.226022, bitrate: 4341 kb/s
> Stream #0.0[0x1e0], 29.97 fps(r): Video: mpeg2video, yuv420p, 720x480,
> 7000 kb/s
> Stream #0.1[0x80]: Audio: ac3, 48000 Hz, 5:1, 448 kb/s
> Output #0, rawvideo, to 'pipe:':
> Stream #0.0, 29.97 fps(c): Video: rawvideo, yuv420p, 320x240, q=2-31, 200
> Stream mapping:
> Stream #0.0 -> #0.0
> Press [q] to stop encoding
> Program exited with code 0204.
> (gdb) bt
> No stack.
> (gdb) disass $pc-32 $pc+32
> No registers.
> (gdb) info all-registers
> The program has no registers now.
Odd, that means that the program has exited normally. Check your cpu
temp to see if it's not overheating. this could your problem.
I am disillusioned enough to know that no man's opinion on any subject
is worth a damn unless backed up with enough genuine information to
make him really know what he's talking about.
-- H. P. Lovecraft (about the flamewars on FFmpeg and MPlayer-dev mailing lists)
More information about the ffmpeg-devel