Re: Problem with Native Application Debugging with Win CE 6.0R2 an

Hello Michel,

Thanks for your comments.

It does work. That is, the debugger does break at the marked statement.

It's just that, one has to locate the relevant debug message, out of host of
these unwanted stuff.

Thanks again and Best Regards,

Vijay Vaidya

"Michel Verhagen [eMVP]" wrote:

But is it working? Does the debugger break at the breakpoint? If it
does, what is the big deal with these messages on the serial?

Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Vijay Vaidya wrote:
Hello,

- We are working with AMD Geode LX800 Board. The development platform we
are using is VS2005 and Win CE 6.0 R2 with VS2005 with SP1.

- The development machine is XP Professional with SP2

- We have successfully made the OS image with the BSP that came with
the board.

- We are using CoreCon for VS2005 connection and we are able to connect
the target board successfully.

- We prepared the SDK for this target baord and installed it on the
same developemnt machine.

While writting native applications we selected this taget platform.

- As we are still in the development process we are working with Debug Build
Configuration. We are using a Hyperterminal window for observing Debug Port
messages.

- The application we are working on is a VB application that has
native mode helper dll.

- For this we wrote test .net applications and we are able to Run (Cntl + F5)
and debug (F5) these test .net applications successfully.

- When we started working with test native applications we observed a strange
thing. During the fault finding process, we finally wrote a simple empty
console application that looked as follows.

*****************************************************

// TestDevProj01.cpp : Defines the entry point for the console application.
//

#include "stdafx.h"
#include <windows.h>
#include <commctrl.h>


int _tmain(int argc, _TCHAR* argv[])
{
return 0;
}

*****************************************************

- (Cntl + F5) secnario works as expected. We don't receive any of the
messages mentioned below on the debug port output.

- When we set a breakpoint at 'retuen 0' statement and press F5 we see
a host of follwoing messages on the Debug Port that are quite annoying.

!!!NOT SUPPORTED: Calling MapPtrToProcess!!!!!

ERROR!!! Calling SetKMode
ERROR!!! Calling xxx_SetProcPermissions

ERROR!!! Calling xxx_SetProcPermissions


- As can be seen, the application is not calling any of these deprecated
APIs.

- We searched the net and found out that there are few threads talking
about such problems. These threads said that these messages are coming
out of the process edm.exe that the VS2005 debugger uses to monitor
the remote device process and are such harmless.

- These threads also indicated that VS2005 uses a version of edm.exe
that is for written for earlier CE versions.
Obviously, as the said directory is
'F:\VS2005\SmartDevices\Debugger\target\wce400\x86'
on our machine.

Surprisingly, none of the threads that mentioned these problems terminated
in pointers towards the solution.

- Our question is,
- Is our conclusion that such behaviour is because of 'ealier
version of edm.exe' is correct.
- If so, what is the solution / any workaround
to avoid these annoying messages on the Debug Port.

- Any help will be higly appreciated.

Vijay Vaidya


.

Relevant Pages
Quantcast