After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 340605 - Lock readonly buffers when running under Valgrind?
Lock readonly buffers when running under Valgrind?
Status: RESOLVED WONTFIX
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other All
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-05-04 10:05 UTC by Maciej Katafiasz
Modified: 2009-05-07 19:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Maciej Katafiasz 2006-05-04 10:05:39 UTC 
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.
Comment 1 Tim-Philipp Müller 2006-05-17 10:25:57 UTC 
This sounds like something that one would only want to enable with special configure switches, as buffer refcounting is usually done atomically and you'd have to (a) check for the special mode case and (b) use normal locks to do all this in a thread-safe way otherwise if I'm not mistaken. Depends on whether we want to avoid (a) in normal operation I guess.

Anyway, got a patch?
Comment 2 Sebastian Dröge (slomo) 2009-05-07 19:53:46 UTC 
As there wasn't any progress in years I'll close this bug for now as we usually don't keep such feature request unless someone is working on it.