Valgrind output and memory leaks

[Dan Meltzer]

Here's another, with leak-check=full...

On Thu, Feb 12, 2009 at 12:29 AM, Mark Kretschmann <kretschmann at kde.org> wrote:
> On Wed, Feb 11, 2009 at 11:25 PM, Myriam Schweingruber
> <schweingruber at pharma-traduction.ch> wrote:
>> Hi all,
>>
>> find attached an output I got with the following command:
>>
>> valgrind --log-file=$HOME/... --leak-resolution=high --num-callers=40
>> -- amarok -m -d --nofork
>>
>> I only loaded an album into playlist, played two songs, then quit with ctrl+Q
>>
>> Greets
>>
>> Myriam
>>
>> PS. If I should run other test, just ping me, my laptop is pretty fast
>> and idle most of the time :)
>
> Sorry, what I forgot to tell you is that you might also need to add
> --leak-check=full to get a useful leak analysis. Again sorry for the
> oversight.
>
> --
> Mark Kretschmann
> Amarok Developer
> www.kde.org - amarok.kde.org
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: amarok-valgrind.log.gz
Type: application/x-gzip
Size: 71298 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/amarok-devel/attachments/20090212/cea7b525/attachment-0001.gz