On 28 Oct 2010, at 22:12, Tobias Giesen wrote: > Jonas wrote: > >> export MallocStackLogging=1 >> Then, once the program is running and has leaked memory, run >> leaks nameofyourprogram > > Thanks for this tip! It is very interesting, however in this situation > it does not detect the lost memory.
You can also run the program under valgrind with its default tool (memcheck). It will trace all memory allocations (rather than scanning the heap for potential pointers to memory blocks) and should be able to pinpoint where the unfreed allocations are happening. Jonas_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
