Le 07/06/2012 22:50, Martin a écrit :
On 07/06/2012 09:20, Antonio Fortuny wrote:
1 unfreed memory blocks : 16  <<=========================== sounds OK
True heap size : 786432 (160 used in System startup)
True free heap : 813088
Should be : 786128
Call trace for block $0000000000086ED0 size 16    <<========================== this is OK
  $000000000040FE8E
  $0000000000540A19
  $0000000000531EF9
  $000000000050E44A
  $0000000000586FA9
  $000000000052DC99
  $000000000053B4C7
  $00000000005B5237

Maybe the very first address is somewhere without debug info?
Maybe. But in any case, the very last is inside the program:
procedure TForm1.BtnConnectClick(Sender: TObject);
var
  pc: PChar;
begin
  pc := nil;
  ReAllocMem(pc, 16);
  ConnectDB;
  BtnConnect.Enabled := False;
  BtnDisconnect.Enabled := not BtnConnect.Enabled;
  BtnConnect.Enabled := False;
  GrQuery.Enabled := True;
  GrSerialTest.Enabled := True;
  GrSmallTests.Enabled := True;
  AllowQueryButtons(False);
end;

The problem is that the stackdump permamently stops resolving, once this happens.

Since you are on 1.1
yes in Vista WIN32 but not in my current development platform: Windows server 2003 x64
Lararus 0.9.31.
please install the package LeakView - then go to tools menu and open the leak view window
load the data
I've installedthe package leakview but it does not help really:
.

there is a button "resolve". select the exe that leaked. it is a new feature. it SHOULD resolve any address for which symbols exist


--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply via email to