Re: Loaded memory image differs from map file

Mariella Bakker wrote:

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


there are 2 things that i can tell you.

#1.
The last time i looked, the map file was a zero base file and the
image file when loaded gets the base offset added to it.
$00400000 rings a bell for the offset, if this is what your seeing then simply place in your mind to subtract that from the report you get
to make it simpler to find your code point.

#2..
your report address may not drop on an exact address but but in between some where.. this should get you close to the problem.
it's usually the code line you find in your map file just prior the
address reported where the fault lye's.



--
Real Programmers Do things like this.
http://webpages.charter.net/jamie_5

.

Relevant Pages

  • Loaded memory image differs from map file
    ... With a certain project I am facing troubles profiling it. ... call on an interface pointer. ... When comparing the EIP address with the map file, ... but that address corresponds with different Delphi source ...
    (comp.lang.pascal.delphi.misc)
  • Re: Strange access violations
    ... always generate a mapfile for each release ... when a report is given you, ... open the MAP file and remove the ... >>is easy enough that a causal user can run it? ...
    (comp.lang.pascal.delphi.misc)
  • Re: Process Profiling
    ... how to make the .map file of my application to create the profile header in ... > applications profiling is not shown. ... > Vivek B. ...
    (microsoft.public.windowsce.embedded)