[Gstreamer-bugs] [Bug 101571] Changed - use of asm/atomic.h on i386 SMP machines can result in random segfaults

[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=101571

Changed by dlehn at vt.edu.

--- shadow/101571	Wed Dec 18 21:15:23 2002
+++ shadow/101571.tmp.8677	Wed Dec 18 21:38:26 2002
@@ -10,13 +10,13 @@
 Component: gstreamer (core)
 AssignedTo: gstreamer-maint at bugzilla.gnome.org                            
 ReportedBy: dlehn at vt.edu               
 QAContact: gstreamer-maint at bugzilla.gnome.org
 TargetMilestone: 0.4.0
 URL: 
-Summary: use of asm/atomic.h on SMP machines can result in random segfaults
+Summary: use of asm/atomic.h on i386 SMP machines can result in random segfaults
 
 The use of #include <asm/atomic.h> in gst/gstatomic.h is problematic.  It
 can lead to the atomic code being compiled without the use of the "lock"
 instruction.  This is a critical error on SMP machines.  Random crashes can
 happen without "lock".  This has been observed for me as a crash when a
 subbuffer is alive but it's parent has been unrefed and freed.  Accessing
@@ -49,6 +49,10 @@
 HAVE_ATOMIC_H check and asm/atomic.h usage.  Code would then fallback on to
 the GMutex atomic operations.  This would probably cause performance hit on
 some archs.
 
 Marked as critical due to segfaults at random locations on SMP machines. 
 This is probably not an issue at all on UP machines.
+
+------- Additional Comments From dlehn at vt.edu  2002-12-18 21:38 -------
+I should note this is a problem on i386 SMP.  Does anyone know if this
+is also a problem on other SMP architectures?