CE 6.0 debug using KITL and Kernel debugger

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Victor - 30 Oct 2008 07:18 GMT

Hi,
I am using PXA270 + Windows CE 6.0
When I enable the build option of KITL and Kernel debugger and debug
remotely, the VS2005 CE6 interface will pop out an dialog asking for the
following directory:

d:\yamafp-1\private\winceos\coreos\core\thunks

This can not be found anywhere in my CE 6.0 environment.
Even I disable KITL and Kernel and only build using debug build, there are
hundreds of message about
--------------------------------------------------------------------------------
Coredll: DEBUGCHK failed in file
D:\yamafp-1\private\winceos\COREOS\core\thunks\krn\..\tkmarshal.cpp at line
421
DEBUG_BREAK @c0062714 Ignored.
Coredll: DEBUGCHK failed in file
C:\yzkiqfe\private\winceos\COREOS\core\lmem\.\rheap.cpp at line 1374
DEBUG_BREAK @c006ace4 Ignored
-------------------------------------------------------------------------------

Questions:
1. What are those?
2. How can I get rid of them?

Reply to this Message

Luca Calligaris - 30 Oct 2008 08:12 GMT

In debug mode only DEBUGCHK check for a TRUE/FALSE condition and if it
results FALSE it triggers a debug break;
the break is ignored if you have no debugger; if you run a release version
DEBUGCHK will be ignored. Take in account
that even in a release build you can:
1)enable the kernel debugger
2)enable KITL
3)use the COMPILE_DEBUG switch in sources file to compile selected modules
in debug mode.

Obviously the best solution would be identifying why you're hitting the
DEBUGCHK...

HTH

Signature

Luca Calligaris
l.calligaris.nospam@eurotech.it.nospam
www.eurotech.it

> Hi,
> I am using PXA270 + Windows CE 6.0
[quoted text clipped - 21 lines]
> 1. What are those?
> 2. How can I get rid of them?

Reply to this Message