[gstreamer-bugs] [Bug 451276] New: Checks are not thread safe

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=451276

  GStreamer | gstreamer (core) | Ver: HEAD CVS
           Summary: Checks are not thread safe
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: thaytan at mad.scientist.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Each fail_if and fail_unless call to libcheck sends the current execution
position to the parent process, so it can write some information about where
the child crashed in case it does.... but there's no locking in libcheck and we
call the macros from lots of different threads in our tests.

I think this may be the cause of an intermittent "Bad message type arg" error
I'm getting in the core tests/check/elements/multiqueue test.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=451276.