administrator/blaise
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

feat(debug): show refcount per object in leak report

Browse source 
Each leaked object line now reports its refcount: `- ClassName (rc=N)`.
This distinguishes the two leak modes at a glance:

  rc=1  reference created but never released (dangling owner)
  rc>1  over-retain — an AddRef without a matching Release (double-AddRef)

Reads the refcount from the class header at UserPtr - CLASS_HDR.  Adds a
WriteSignedInt helper since immortal objects report rc=-1.
This commit is contained in:
Graeme Geldenhuys 2026-06-01 23:55:51 +01:00
parent 043602a0a4
commit ebe131da15
1 changed files with 24 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
runtime/src/main/pascal/blaise_arc.pas
View file

@ -234,6 +234,20 @@ begin
_libc_write(STDERR_FD, @Buf[Pos + 1], Int64(19 - Pos));
end;
procedure WriteSignedInt(V: Integer);
var
Neg: Byte;
begin
if V < 0 then
begin
Neg := Ord('-');
_libc_write(STDERR_FD, @Neg, 1);
WriteInt(-V);
end
else
WriteInt(V);
end;
procedure _LeakTrackerReport;
var
I: Integer;
@ -242,6 +256,8 @@ var
ClassName: Pointer;
LenSlot: ^Integer;
NameLen: Integer;
RCSlot: ^Integer;
RC: Integer;
begin
if not GLTEnabled then Exit;
if GLTCount = 0 then Exit;
@ -270,6 +286,14 @@ begin
end
else
WriteStr('(unknown)', 9);
{ Refcount lives in the class header at UserPtr - CLASS_HDR. A leaked
object with rc>1 indicates an over-retain (double-AddRef); rc=1
indicates a reference that was never released. }
RCSlot := Slot^ - CLASS_HDR;
RC := RCSlot^;
WriteStr(' (rc=', 5);
WriteSignedInt(RC);
WriteStr(')', 1);
WriteNL;
end;
end;