in7y118 at public.uni-hamburg.de
Fri Apr 9 07:35:15 CEST 2004
On Wed, 7 Apr 2004, Ronald S. Bultje wrote:
> On Mon, 2004-04-05 at 23:58, Benjamin Otte wrote:
> > 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.
> How about an command-line option to turn this on if wanted? Then you
> don't have this issue.
I'm not sure exposing valgrind functionality to end users (and those are
using command line args) is a good idea.
So I didn't do this. For now there's only one change: Memchunks use
anonymous mmap to get memory under valgrind instead of malloc, because
using malloc breaks valgrind.
More information about the gstreamer-devel