Re: FastMM <-> MemCheck

OBones wrote:
....
> That is valid when you are developping from sratch. But when you are
> overtaking a program with a 10 year history of not caring about memory
> leaks, I find it very good to simply have a report at the end with all
> the leaks in details just like MemCheck does.

Right. But it does not hurt to run FastMM with all bells&whistles, to catch
the more serious bugs like buffer overflow etc. It does not matter if a
project is new or a decade old, such bugs should be smashed rigorously. And
after some months of using MemCheck and healing one leak after another, it
could be a good idea to give the FastMM reporting feature a new try.

Ralf


.

Relevant Pages

  • Re: FastMM <-> MemCheck
    ... overtaking a program with a 10 year history of not caring about memory leaks, I find it very good to simply have a report at the end with all the leaks in details just like MemCheck does. ... But it does not hurt to run FastMM with all bells&whistles, to catch the more serious bugs like buffer overflow etc. ... And after some months of using MemCheck and healing one leak after another, it could be a good idea to give the FastMM reporting feature a new try. ...
    (borland.public.delphi.non-technical)
  • Re: GC.Collect can be trusted?
    ... on the allocation pattern. ... small managed memory leaks by using a profiler alone. ... I can tell you now that I have very little time to spend tracking down bugs in the GC. ... What I'm after is being able to track down memory leaks that I unwittingly create in the code I write. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: FastMM and memory leaks
    ... I used to see a lot of messages like that when I was using Memproof - I subsequently switched to using MemCheck ... It'll give you line numbers and all sorts of useful info if it finds any leaks - but be sure to configure your project options ... and Include TD32 Debug Info on - then rebuild and run. ... You'll have to enable a few compiler switche options in that file: ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: FastMM <-> MemCheck
    ... FastMM gives you immediate response. ... You can identify remaining leaks with MemCheck or MemProof. ... It is possible that you have to comment out FastMM for the mem check run. ...
    (borland.public.delphi.non-technical)
  • Re: Memory eating...
    ... memcheck doesn't report any leaks. ... I suspect that in some cases, ...
    (comp.unix.programmer)