Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2013-11

laz 1.3 unfreed memory block

2 messages · 1 person ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

waldo kitty

Lazarus 1.3 r42488 FPC 2.7.1 r26006 i386-win32-win32/win64

just updated and compiled fpc and laz... opened laz with default blank project and closed laz (after getting above version info)...

Heap dump by heaptrc unit
776442 memory blocks allocated : 76059123/78081992 776443 memory blocks freed : 76059188/78082064 1 unfreed memory blocks : 144
True heap size : 720896 (128 used in System startup) True free heap : 720512
Should be : 720448

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?

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.

Reply by email

waldo kitty
to waldo kitty

On 11/10/2013 8:19 AM, waldo kitty wrote:
[...]

Show quoted text 7 lines
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.

Reply by email