On Sat, Dec 30, 2006 at 09:23:38AM +0200, Yavor Doganov wrote: > On Fri, Dec 29, 2006 at 02:45:14PM -0800, David Schleef wrote: > > Could you run: > > > > rm ~/.gstreamer-0.10/registry.*.xml > > GST_DEBUG=*:3 gst-launch --gst-debug-no-color > > > > and attach the output? > > Attached is the output produced on my machine running unstable.
Now try: rm ~/.gstreamer-0.10/registry.*.xml gdb -args gst-launch-0.10 --gst-disable-registry-fork and give gdb the command 'run'. GDB will stop once with a SIGILL in the function 'test_altivec()' called by 'oil_cpu_fault_try()'. Use the command 'c' to continue when this happens (since it's not a problem). It should stop again with a SIGILL. Please capture the backtrace at this point and attach it to the bug. Just in case I forgot about some other CPU detection code, please enter 'c' again. It should say something like "Process Terminated, killed by signal". If it doesn't, it will probably continue along until it hits another SIGILL, at which point you should create a second backtrace. As an off the cuff guess, it's probably due to the ffmpeg plugin, /usr/lib/gstreamer-0.10/libgstffmpeg.so. You could attempt removing that to see if it starts working. (The test command above is bogus and will print an error, but it's not supposed to crash.) dave... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
