[Lazarus] laz 1.3 unfreed memory block

[waldo kitty]

On 11/10/2013 8:19 AM, waldo kitty wrote:
[...]
> this is all i get and my lazdbg.log file is not created any more so i can't get
> any info from there... i suspect this has to do with my using
>
>    OPT="-gl -gh -dHEAPTRC_WINDOW"
>
> when i make laz... any ideas on how i can have both, the window i can c'n'p from
> and the debug log file?

i may have figured this out... i (finally??) set the HEAPTRC environment 
variable to point to my desired log file and removed the "--debug-log=filename" 
from my lazarus command line... now i do get the log file, no popup and the 
contents of the log show 0 unfreed memory blocks...

FWIW: i tried this with startlazarus and always got an error when lazarus exited 
that it could not open the desired log file... when this happened, it said that 
it was writing all the output to stderr or stdout (i forget which and never get 
anything in the console screen used to start lazarus)... looking at the log 
file, after i discovered that it existed and contained something, i saw that it 
was related to startlazarus so apparently startlazarus was using the file and 
had it locked for its use only... so i've switched back to using lazarus.exe 
directly...


-- 
NOTE: No off-list assistance is given without prior approval.
       Please keep mailing list traffic on the list unless
       private contact is specifically requested and granted.