Hi,

I just installed Platform Builder 5.0 and Post Mortem Debugger.
When I'm opening kdmp file, it's opening without any trouble, but I
cannot see any symbols loaded when I run the project.
It just shows ProgramName!Address

I have map files and executables in the same directory. I tried to enter
path to map files, and load symbols again, but it does not help.
Can anyone have idea what it could be?

regards
Marcin

Re: Problem with symbol loading by Luca

Luca
Wed Feb 06 03:05:16 PST 2008

Never used post mortem debugger, anyway do you have the .pdb files?

--

Luca Calligaris
www.eurotech.it

"klops" <klops@op.pl> ha scritto nel messaggio
news:%23YTNixKaIHA.2000@TK2MSFTNGP05.phx.gbl...
> Hi,
>
> I just installed Platform Builder 5.0 and Post Mortem Debugger.
> When I'm opening kdmp file, it's opening without any trouble, but I cannot
> see any symbols loaded when I run the project.
> It just shows ProgramName!Address
>
> I have map files and executables in the same directory. I tried to enter
> path to map files, and load symbols again, but it does not help.
> Can anyone have idea what it could be?
>
> regards
> Marcin



Re: Problem with symbol loading by Valter

Valter
Wed Feb 06 03:15:50 PST 2008

klops <klops@op.pl> wrote in
news:#YTNixKaIHA.2000@TK2MSFTNGP05.phx.gbl:

> Hi,
>
> I just installed Platform Builder 5.0 and Post Mortem Debugger.
> When I'm opening kdmp file, it's opening without any trouble, but
> I cannot see any symbols loaded when I run the project.
> It just shows ProgramName!Address
>
> I have map files and executables in the same directory. I tried to
> enter path to map files, and load symbols again, but it does not
> help. Can anyone have idea what it could be?

You need PDB and not .map files to allow the post mortem debugger
(both the standalone tool and the one integrated in Visual Studio 2005
with Platform Builder) to convert addresses to references to your
code.
On a release build you may not have a perfect correspondence between
code lines and the generated machine code because the optimizer may
mix code from different C statements to optimize the pipelines etc.
So don't consider the line reported as the only one that may have
generated the fault but check also the .cod file to understand clearly
what gerated the fault (some assembly knowledge is required...) or, if
you don't like to mess with asm, consider the whole code block and not
the single line for possible fault reasons.


--
Valter Minute
www.fortechembeddedlabs.it
Training, support and development for Windows CE
(the reply address of this message is invalid)