Newsgroups : Borland : borland.public.delphi.nativeapi.win32 : 2006 Jun : Access Violation in NTDLL
| Subject: | Access Violation in NTDLL |
| Posted by: | "Jon Robertson" (jonrobertson@medevolve.dontspamme.com) |
| Date: | 19 Jun 2006 09:17:57 |
I'm trying to track down an Access Violation in NTDLL.DLL. I've added
JCLDebug to our application and I've got a stack trace.
It looks like the AV is occurring in RTLAllocateHeap, which is called by
System._HandleException. For D6, Update 2, RTL Update 2, this is (Line
9362, "system.pas" + 13) + 0
According to MSDN, an Access Violation is thrown by RTLAllocateHeap
"because of heap corruption or improper function parameters."
Based on this information, it would appear that the actual exception in
the application is not an AV in NTDLL, but rather System._HandleException
is getting an AV in NTDLL while trying to handle the original exception.
This would certainly explain the large number of AVs in NTDLL that our
users receive.
Has anyone seen this before? Any pointers on how I can track down the
original exception? Any pointers how I can resolve whatever is causing
the AV in RTLAllocateHeap? Would implementing FastMM help any, since this
error seems to be related to allocating Windows heap, not Delphi's own
memory management?
Thanks!