12 Feb 2004 iagorubio   » (Journeyer)

Dealing with memory

Preparing cssed for a new release, I was wondering about memory management.

I checked - not one but twice - all buffers allocated by cssed were released, but the doubt was in the air.

I didn't like very much memprof, so I decided to try valgrin.

The results of the tests where doubly satisfactory: I didn't find memory leaks in cssed's code, and I find a great tool for memory checking.

valgrid did a great job, checking the program for memory problems.

I build some test apps, to check results, and it found every memory leak and race condition, pointing to source file and line number.

I'm sure it's in my tool box to stay ;)

You've got it here http://valgrind.kde.org/

Latest blog entries     Older blog entries

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!