If you have a QA add-in like EurekaLog, make sure FastMM is decared before it in your project source. By default, these add-ins place their declaration first when activated for a project which leads to problems.
HTH Roland -----Original Message----- From: delphi-boun...@elists.org [mailto:delphi-boun...@elists.org] On Behalf Of Jeremy North Sent: Monday, 15 June 2009 9:34 AM To: Borland's Delphi Discussion List Subject: Re: AV with Delphi 7 On Sun, Jun 14, 2009 at 1:49 AM, Sid Gudes<s...@piasystems.com> wrote: > Since the situation is deterministic, try removing FastMM and reverting to > the Delphi native memory manager, and see if the problem goes away. If the > problem stays, it's not FastMM. If the problem goes away, it probably is > (unless it's some sort of whacky bad pointer that Delphi's MM can handle but > FastMM cannot, but that's an unlikely case). Just because the problem may "go away" when using the default MM is probably a bad sign. I'd say the issue is with your code somewhere and FastMM is a bit more rigid than the default MM. Have you switched on all of the debug options for FastMM? You could try and contact Pierre and see if he can offer you any assistance. _______________________________________________ Delphi mailing list -> Delphi@elists.org http://lists.elists.org/cgi-bin/mailman/listinfo/delphi _______________________________________________ Delphi mailing list -> Delphi@elists.org http://lists.elists.org/cgi-bin/mailman/listinfo/delphi
