[Gstreamer-bugs] [Bug 112086] New - GStreamer needs working threading

[bugzilla-daemon at widget.gnome.org]

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=112086

Changed by in7y118 at public.uni-hamburg.de.

--- shadow/112086	Fri May  2 12:03:39 2003
+++ shadow/112086.tmp.15307	Fri May  2 12:03:39 2003
@@ -0,0 +1,31 @@
+Bug#: 112086
+Product: GStreamer
+Version: HEAD CVS
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: critical
+Priority: Normal
+Component: gstreamer (core)
+AssignedTo: gstreamer-maint at bugzilla.gnome.org                            
+ReportedBy: in7y118 at public.uni-hamburg.de               
+QAContact: gstreamer-maint at bugzilla.gnome.org
+TargetMilestone: 0.6.x
+URL: 
+Summary: GStreamer needs working threading
+
+gst-launch { priority=3 fakesrc num-buffers=1 ! fakesink }
+
+will probably run into a trace/breakpoint trap.
+In my gdb it locks forever.
+On some rare occasisons it might even work.
+On the multi-CPU Solaris machine it's doing some weird mad stuff I don't
+even understand.
+
+I'm opening this as bug, because I want to have a general consensus on how
+we handle access to members of different objects. Particularly interesting
+are element->current_state and element->pending_state for this case.
+
+I'd propose to clearly define who may read/write to each member of each
+element or which lock is needed to access it.