Loaded memory image differs from map file
- From: "Mariella Bakker" <mariella.nospam@xxxxxxxxxxxxx>
- Date: Tue, 22 Nov 2005 09:44:37 +0100
With a certain project I am facing troubles profiling it. At a certain
point, the profiling application will die with an Access Violation. The code
where the profiling application fails, is a call to an interfaced method
call on an interface pointer. When debugging with Delphi, and setting a
breakpoint before this call, the compiler will stop on a different location
than the call (Somewhere in the middle of a different call of a different
class of the same unit). When comparing the EIP address with the map file,
the EIP contains the address where the called method should exist according
to the .map file, but that address corresponds with different Delphi source
code.
Strange enough, when I comment a certain normal object (descendent of
TCollectionItem) out, the debugger will stop on the correct line of source
code. The commented out object is an object which is not used, is not
interfaced, and besides some fields and properties only contains an Assign
method.
Does anybody have any idea what is happening here?
Regards,
Mariella Bakker
.
- Follow-Ups:
- Re: Loaded memory image differs from map file
- From: Jamie
- Re: Loaded memory image differs from map file
- Prev by Date: Re: Checkbox with colored background?
- Next by Date: How to set initial proportions of stacked aligned panels?
- Previous by thread: Drawgrid - no selection
- Next by thread: Re: Loaded memory image differs from map file
- Index(es):
Relevant Pages
|
|
