[Gstreamer-bugs] [Bug 93735] Changed - Crash with gst-launch cdparanoia ! spider ! osssink
bugzilla-daemon at widget.gnome.org
bugzilla-daemon at widget.gnome.org
Sat Oct 26 02:31:09 PDT 2002
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=93735
Changed by rbultje at ronald.bitfreak.net.
--- shadow/93735 Wed Sep 25 19:32:03 2002
+++ shadow/93735.tmp.25041 Sat Oct 26 05:31:09 2002
@@ -129,6 +129,21 @@
gstbasicscheduler.c:271
271 G_GNUC_UNUSED const gchar *name = GST_ELEMENT_NAME (element);
(gdb) bt
#0 gst_basic_scheduler_loopfunc_wrapper (argc=134769064, argv=0x0) at
gstbasicscheduler.c:271
(gdb)
+
+------- Additional Comments From rbultje at ronald.bitfreak.net 2002-10-26 05:31 -------
+As Wim suggested, the problem was a state change failure. The point
+for me was to find out which element caused the state change failure
+(just browse through the --gst-mask=-1 output and grab a cop of
+coffee, probably two or more ;-) ), and fix the cause of why the
+state_change failed. In my case, it was an uninitialised variable
+(filesink->location wasn't set).
+
+Hope this helps a bit... I was getting the weirdest unusable
+backtraces, so they weren't really helpful. --gst-mask=-1 (or
+--gst-mask=0x0100040, that just gives state change and capsnego
+output). If that doesn't help, add some debug info to the state_change
+fuctions of the plugins you're using and see which one fails... It's
+quite some work, I know, but it worked for me.
More information about the Gstreamer-bugs
mailing list