VxWorks Debugger Problem

[esha.bh...@gmail.com]

Hi,

I'm trying to get the Tornado debugger working and I get the
following error message when I try to connect the target server to the
WDB back end on the target.

Connecting to target agent... succeeded.
Attaching C++ interface... succeeded.
Attaching elf OMF reader for PPC CPU family... succeeded.
Warning: Target checksum: 0xa945 (computed from 0x100000 to 0x1b8290).
Host checksum: 0x6876 (computed from 0x11a0080 to 0x1258310).
Warning: Core file checksums do not match.

I have made sure that the kernel files on the target and the host PC
that runs the target server are identical.

Any hints?

Thanks
E

[Michael R. Kesti]

esha.bh...@gmail.com wrote:

<snip>

> Warning: Target checksum: 0xa945 (computed from 0x100000 to 0x1b8290).
> Host checksum: 0x6876 (computed from 0x11a0080 to 0x1258310).
> Warning: Core file checksums do not match.

<snip>

This is almost always a matter of not correctly setting the target
server's "Core File and Symbols" property. See section 8.2.2 and
figure 8-5 of the Tornado User's Guide.

--
========================================================================
Michael Kesti | "And like, one and one don't make
| two, one and one make one."
mke...@gv.net | - The Who, Bargain

[esha.bh...@gmail.com]

Michael

Thanks for the response. As I indicated in my original email, we have
made sure all these settings are right and we have ensured that we are
using the identical kernel file (same as that used on the target) for
the Core File and Symbols. We still end up with the same warning.

I went through the user guide and could not find any other trouble
shooting tips regarding this problem.

Thanks
Murali

[David Lindauer]

we had the same problem at one point... I am not sure how we got it fixed,
it may have been by rebuilding the entire project, or it may have been by
deleting the target server entry and starting from scratch. Or we may have
had something else we had to do... I did notice that at least one of my
target server entries doesn't seem right somehow, I have TCL scripts to read
values from them and they aren't reading correctly...

David

[umts]

I have also met this problem. But I can launch windshell and debug on
Host machine. I have contach WindRiver support. They said this maybe
due to the size of symbole file.
My symbole file is about 700M. In the latest release(workbench) should
have solved the problem.