Re: [fpc-pascal] Leak narrowed down

2010-10-28 Thread Andrew Brunner
>> 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. > > At this point I have to give up on GetTextWidth - I will avoid it for > now. Maybe next yea

Re: [fpc-pascal] Leak narrowed down

2010-10-28 Thread Jonas Maebe
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 memo

Re: [fpc-pascal] Leak narrowed down

2010-10-28 Thread Luca Olivetti
Al 28/10/10 22:12, En/na Tobias Giesen ha escrit: At this point I have to give up on GetTextWidth - I will avoid it for now. Maybe next year the problem can be solved. I will send a note to the Lazarus list and submit a bug report, provided I can confirm the issue with a minimal testing program

Re: [fpc-pascal] Leak narrowed down

2010-10-28 Thread Tobias Giesen
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. At this point I have to give up on GetTextWidth - I will