<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 12/06/2012 14:14, Antonio Fortuny wrote:
<blockquote cite="mid:jr7faq$b5c$1@dough.gmane.org" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
<blockquote cite="mid:4FD11431.80209@mfriebe.de" type="cite"> <br>
there is a button "resolve". select the exe that leaked. it is a
new feature. it SHOULD resolve any address for which symbols
exist<br>
</blockquote>
But it does not really <span class="moz-smiley-s7"><span> :-\ </span></span><br>
<br>
I've prepared a new virtual machine with W7-Win32<br>
Lazarus full 1.1 from 2012-06-11 + WinCE for cross-compile<br>
Made a very simple project (one form, two buttons one to create a
memory leak, one to close)<br>
Redirect heaptrc output to a file<br>
Set compiler options for compiler and linker:<br>
-g automatic debugger<br>
-gl add line numbers<br>
-gh use heaptrc<br>
-WG win32 program<br>
compile, link and run and get this:<br>
<i><b>c:\sources\compiled\TestUib.Exe </b></i><i><b><br>
Call trace for block $001D62B0 size 16</b></i>
<<======== my block, looks OK<br>
<i><b> $0040D628<br>
$004FAA4E TCONTROL__CLICK, line 2735 of
./include/control.inc<br>
</b></i>the result whether I use -gs or -g. I can easily guess
that both blank lines with only an address are the two lines of my
project<br>
I've installed leakview but the Resolve button resolves anything
with the project.exe<br>
Thea ddress <i><b>$0040D628</b></i> corresponds to the function
Reallocmem function used to get the memory block<br>
</blockquote>
<br>
can you try <br>
<br>
gdb.exe <i><b>c:\sources\compiled\TestUib.Exe</b></i><br>
<br>
info line *0x0040D628<br>
<br>
The whole thing is rather odd. From what you described, you done the
correct steps. And it works, if I do it here (vista 32 bit). Though
I use the released fpc 2.6.0 (that may still be an idea)<br>
<br>
I can only see 2 reasons.<br>
1) For some reason, fpc did not write or link symbol info for your
unit.<br>
2) The stabs reader in fpc has problems reading it ("resolve" uses
the same reader)<br>
<br>
In case 2 gdb should be able to read it.<br>
</body>
</html>