FastMM478 flagging ordinary statements

When I run FastMM on my D2006 app it complains on statements that use:

UpperCase, DateTimeToStr, and HyperStr's Parse function.

Since these functions are in a loop, it will flag them thousands of times. The log file is a whopping 755k lines. (Should I post it? - Just kidding.)

If I write a test application and put these same functions in it, FastMM does not flag them when they are executed. Are these functions something I should be concerned with? Is there a way to remove these procedure names so they won't be checked by FastMM? (Otherwise it takes 5 minutes to write out the log file.)

TIA

Sam
.

Relevant Pages

  • Reading from log
    ... danield writes: ... > I am looking for help with creating a digest of a log file. ... Then when you go thru the loop again, ... test the flag to see if it is set. ...
    (perl.beginners)
  • Possible FastMM4 w/Optimization bug
    ... Here is a link to a movie file showing the problem... ... previously experiencing with NexusMM 3 in a different section of code ... with a for loop. ... I haven't tried that yet with FastMM. ...
    (borland.public.delphi.language.basm)
  • Re: Possible FastMM4 w/Optimization bug
    ... > similar line of code with their MM and with optimizations turned on. ... > problem I was previously experiencing with NexusMM 3 in a different ... > section of code with a for loop. ... I haven't tried that yet with FastMM. ...
    (borland.public.delphi.language.basm)
  • Re: Optimizing Delete
    ... But that does not really count because there is not much memory management needed running the plain loop. ... With FastMove and FastMM: about 10 seconds ...
    (borland.public.delphi.language.basm)
  • Re: FastMM478 flagging ordinary statements
    ... UpperCase, DateTimeToStr, and HyperStr's Parse function. ... Since these functions are in a loop, it will flag them thousands of ... The log file is a whopping 755k lines. ...
    (borland.public.delphi.thirdpartytools.general)