>Have you tried running your app under Massif? That has helped me >recently to track down a memory leak which was not visible in >Valgrind/Memcheck but became clearly visible in Valgrind/Massif (the >leak was caused by repeated setenv() calls, which apparently don't free >any memory even if the env var is unset later). > Note also that you might also try the "gdbserver" patch, which provides an "incremental leak (or more precisely delta malloc-ed or delta free-d)" "leak search" functionality.
(see http://bugs.kde.org/show_bug.cgi?id=214909 ) Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
