MemCheck only checks the heap. If you have a stack corruption issue, then it will not find it.
Another kind of related issue is timers that don't get deallocated ie still active when their associated window handle is destroyed. Myles. -----Original Message----- From: Rohit Gupta [mailto:[EMAIL PROTECTED] Sent: Wednesday, 25 February 2004 22:15 To: NZ Borland Developers Group - Delphi List Subject: Re: [DUG] Critical Sections We have been using Memcheck for sometime that doesnt find anything. We have been using madExcept to look at the freezing which has been giving us most of the info. Boundschecker... I tried a few days ago. It is wierd. I cant find their site... alll paths lead to devrace and the only version there does not say that it works with Delphi. - instead it appears only for VB. Myles Penlington wrote: >First off get memcheck - it's free. It does spot most issues quite quickly - >but will only spot issues directly related to memory allocations by Delphi's >memory manager. > > http://v.mahon.free.fr/pro/freeware/memcheck > >If that fails, for real serious stuff go buy BoundsChecker from NuMega. > >Myles. > > _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
