<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.6000.16544" name=GENERATOR></HEAD>
<BODY><FONT face=Arial color=#0000ff size=2></FONT>
<DIV><BR><SPAN class=140375011-22082011><FONT face=Arial color=#0000ff
size=2> > </FONT></SPAN>Interesting suggestion, can you point to
some code maybe in the lazarus that does a similar job. Does GetLineInfo inside
do something like this? <BR><SPAN class=140375011-22082011><FONT face=Arial
color=#0000ff size=2> </FONT></SPAN></DIV>
<DIV><SPAN class=140375011-22082011><FONT face=Arial color=#0000ff size=2>I'm
currently experimenting with</FONT> <FONT face=Arial><FONT color=#0000ff
size=2>a variation of dump_stack in system.inc. The first try skips a lot of the
functions found by your initial implementation. Still looking into that.
<BR></FONT></FONT></SPAN><FONT face=Arial color=#0000ff size=2></FONT></DIV>
<BLOCKQUOTE class=im
style="PADDING-LEFT: 5px; MARGIN: 0pt 0px 0pt 5px; BORDER-LEFT: rgb(0,0,255) 2px solid"><FONT
face=Arial color=#0000ff size=2></FONT><FONT face=Arial color=#0000ff
size=2></FONT><FONT face=Arial color=#0000ff size=2></FONT><FONT face=Arial
color=#0000ff size=2></FONT><FONT face=Arial color=#0000ff size=2></FONT>
<DIV><BR>It was before and looking at how much cpu time spent, I will be
probably ready for the next measurement only after the hashing is implemented
:). In you question I see a guess, that the fewer the depth, the less likely
false positives get into view, right?<BR><SPAN class=140375011-22082011><FONT
face=Arial color=#0000ff size=2> </FONT></SPAN></DIV></BLOCKQUOTE>
<DIV class=im
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><SPAN
class=140375011-22082011></SPAN> </DIV>
<DIV class=im
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><SPAN
class=140375011-22082011><FONT face=Arial><FONT size=2><FONT
color=#0000ff>Right. Statistically, the smaller the stack you look at, the
less falls </FONT><FONT color=#0000ff>positives you get.
</FONT></FONT></FONT></SPAN></DIV>
<DIV class=im
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><SPAN
class=140375011-22082011><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV class=im
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><SPAN
class=140375011-22082011><FONT face=Arial color=#0000ff size=2>One reason for
false positives is also that local variables aren't initialised. Procedures
declaring local variables like buf:array [0..1000] of char; can cause a lot of
false positives since the stack space used by the array can contain return
addresses of previously excuted functions. Here the stack unwinding should
help a lot, once it works.</FONT></SPAN></DIV>
<DIV class=im
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><SPAN
class=140375011-22082011><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV class=im
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><SPAN
class=140375011-22082011><FONT face=Arial color=#0000ff
size=2>Ludo</FONT></SPAN></DIV>
<DIV class=im
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><SPAN
class=140375011-22082011><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV></BODY></HTML>