[gstreamer-bugs] [Bug 340605] New: Lock readonly buffers when running under Valgrind?

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=340605
 GStreamer | gstreamer (core) | Ver: HEAD CVS

           Summary: Lock readonly buffers when running under Valgrind?
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: bugs at mathrick.org
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Perhaps a useful mem debugging aid would be locking buffers (or more generally,
MiniObjects) that are not writeable using Valgrind client requests. This would
make it much easier to catch semantics breach, especially as docs for
_object_ref() don't mention writeability right now.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.