Hi, Valgrind reports a memory leak on my program for certain variable. To find out on what case I fail to free variable, I printed some messages before the allocation/deallocation of the relevant variable, say printf("ALLOC\n") before calloc and printf("FREE\n") after free. The funny thing is, when I ran and counted the number of messages, there was equal number of ALLOC messages and FREE messages. Which mean, no memory leak at all. Right now I assume that valgrind falsely detect some memleaks. However, this leaves me some uncomfortable feeling, as if sometime later, my program will cause the computer to explode (ok, exaggeration here :). Any thoughts on that? Btw, I use the standard calloc/free provided by glibc, not some 3rd party ones. TIA. Regards, Verdi -- 5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail +++ GMX - die erste Adresse f�r Mail, Message, More +++