On 21.08.2011 10:26, Christian Wieninger wrote: > But unfortunately valgrind does not give me the information where the leak > is caused. Maybe the reason for this is that a search timer update runs in > a separate thread or because plugins are dynamically loaded shared libraries? > Has anybody an idea how to use valgrind in this case? http://www.e-tobi.net/blog/2006/04/30/speicherlecks-im-vdr-finden You must keep the plugins loaded, otherwise you loose their symbol information. Here's what I have in the Debian package to support this: http://anonscm.debian.org/gitweb/?p=pkg-vdr-dvb/vdr.git;a=blob;f=debian/patches/82_valgrind.dpatch http://anonscm.debian.org/gitweb/?p=pkg-vdr-dvb/vdr.git;a=blob;f=debian/valgrind.supp http://anonscm.debian.org/gitweb/?p=pkg-vdr-dvb/vdr.git;a=blob;f=debian/vdrleaktest Tobias _______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
