[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gstreamer-devel
Subject:    [gst-devel] valgrind
From:       Benjamin Otte <in7y118 () public ! uni-hamburg ! de>
Date:       2004-04-05 21:58:08
Message-ID: Pine.A41.4.44.0404052344290.30058-100000 () public ! uni-hamburg ! de
[Download RAW message or body]

Hi gang,

I have added support for valgrind to the GStreamer core. See the ChangeLog
and source for more details.

Some attempt at a FAQ follows:

What does it do?
It detects memleaks better. Particularly GstBuffer and GstEvent. Basically
everything that is mempooled. (Did I mention we should mempool caps and
structures?)

When does it do it?
If GStreamer is compiled with --enable-debug (it is by default) and
valgrind libs are present (detected via pkgconfig), that support is
enabled.

How does it do it?
Valgrind provides a little lib interface for apps to communicate better
with valgrind. Look at /usr/include/valgrind/*.h - the source is
documented nicely.

Where's the catch?
GStreamer now uses different code inside valgrind than outside. So there
may be a very little chance that bugs only appear inside or outside
valgrind. So don't be too surprised if that happens. GStreamer warns you
about that when it runs inside valgrind.


As always, if there are issues with this, file a bug or ask me on IRC.

Happy bug and leak hunting,

Benjamin



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
gstreamer-devel mailing list
gstreamer-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
[prev in list] [next in list] [prev in thread] [next in thread]