heaptrc output
lazarus / 62-General

----------------------------------------------------------------------
Чебурашка · 2023-11-03 12:45

Is this output from heaptrc senseful?

Code: Bash  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i Heap dump
by heaptrc unit of /opt/mep-
hub/RemotedRecordingService-x86_64-linux69402355 memory blocks
allocated : 30328582835/3056901002469402353 memory blocks freed     :
30328583347/305690105362 unfreed memory blocks :
18446744073709551104True heap size : 163840True free heap :
163200Should be : 163968Call trace for block $00007F7B0F84E9C0 size
96  $000000000043C7E1Call trace for block $00007F7B0F84E880 size 112 
$0000000000460C70  $0000000000481212 
This line is very strange to me:

2 unfreed memory blocks : 18446744073709551104

----------------------------------------------------------------------
Leledumbo · 2023-11-04 13:36

Quote from: Чебурашка on November 03, 2023, 01:45:52 pmIs this output
from heaptrc senseful?
Depends on what you mean by senseful. Basically you have 2 unfreed
memory blocks somewhere, but the offending line (or unit) is not
compiled with lineinfo (-gl) on and therefore, no line information can
be given.

----------------------------------------------------------------------
jamie · 2023-11-04 14:01

more than likely, you corrupted one of the memory items your code and
it hit the management of the heap trace code.

 So, you most likely have a memory boundary violated somewhere in your
code and it should be fixed.

----------------------------------------------------------------------
cpicanco · 2023-11-04 15:39

Thanks to Olly, today I know how to install with fpcupdeluxe and make
heaptrc output human readable stack traces:

https://gitlab.com/freepascal.org/fpc/source/-/issues/40487

https://gitlab.com/freepascal.org/fpc/source/uploads/cb182de9c154d9fc5
351471c72cff8a7/image.png

----------------------------------------------------------------------
Чебурашка · 2023-11-05 10:34

Thanks jamie, this is hinting me. The program has a problem with
memory somewhere, and also this heaptrc log (despite it messed up as
well) confirms it.

----------------------------------------------------------------------
Чебурашка · 2023-11-06 07:34

Quote from: cpicanco on November 04, 2023, 04:39:13 pmThanks to Olly,
today I know how to install with fpcupdeluxe and make heaptrc output
human readable stack traces:

https://gitlab.com/freepascal.org/fpc/source/-/issues/40487

https://gitlab.com/freepascal.org/fpc/source/uploads/cb182de9c154d9fc5
351471c72cff8a7/image.png

Thanks, now I had the chance to read this more carefully in the
desktop pc.

I often struggled with no debug stack traces. Basically, I need also
to recompile the FPC, because the debian package seems built without
debugging flags on.

Thank you for this important suggestion.