Debugging of eVC++ 4.0 application on WinMobile 5.0 using VS2005 dummy project

Debugging of eVC++ 4.0 application on WinMobile 5.0 using VS2005 dummy project

• lihai

  Hi Ram,

  I think there was some communication gap. Anyway let me clear out all the steps including yours. Please follow this step by step

  1. Have a debug 'fld_link.exe' built in eVC4.0.

  2. By Remote File Viewer in VS2005, export 'fld_link.exe' on WinMobile 5.0 device in folder '\Program Files\dummy'.

  3. Create a dummy project using VS2005. In this dummy project, on debugging property page mention the remote executable path as-'\Program Files\dummy\fld_link.exe'

  4. Please open the source file corresponding to fld_link.exe using VS2005

  5. Please load the symbols corresponding to fld_link.exe in tools->Options->Debugging->Symbols in VS2005

  6. Now press F10/F11 in VS2005. If you are pressing F5 then put some Breakpoint in the source file

  7. Now you will be able to debug the application using VS2005

  All steps are clearly mentioned on http://blogs.msdn.com/vsdteam/archive/2006/02/05/525224.aspx

  Hope this helps.

  Regards
  Gaurav

  
  

• Maksim Fralou

  Hi Gaurav,

  Thank you very much, Now I am able to debug my application. Thanks a lot.

  Gaurav, one basic question-

  Since cpp file is opened in VS2005, suppose this cpp file has a eVC++4.0 specific API call that is not supported in VS2005, then this particular API call will be failed during debugging using VS2005. Since I don't want to replace this API to equivalent VS2005 API call, so how i will proceed debugging . My aim is to retain my eVC++4.0. It is doubt, even i didn't test this scenario.

  Gaurav, I need your help for another problem-

  In my application i am hard resetting WinCE4.2 and WinMobile3.0 devices by calling APIs SetCleanRebootFlag and KernelIoControl. It is documented that these APIs call will not work for WinMobile 5.0. For hard reset WinMobile5.0 i am calling ExitWindowsEx API but it only soft reset the device. How to hard reset WinMobile5.0 device .

  Thanks a lot.

  Ram

  
  

• Andrius Bolsaitis

  Hi Jeff,

  After installation of eVCSP4, i am able to launch executable. But still in eVC4.0 workspace, it is not showing that application is being debugged, even i marked the breakpoints.

  Please note following points:

  1. I have a debug 'fld_link.exe' built in eVC4.0.

  2. By Remote File Viewer in VS2005, I exported 'fld_link.exe' on WinMobile 5.0 device in folder '\Program Files\dummy'.

  3. Created a dummy project using VS2005. In this dummy project, on debugging property page i mentioned the remote executable path as-'\Program Files\dummy\fld_link.exe'. On pressing F5 in dummy project, invokes '\Program Files\dummy\fld_link.exe' on WinMobile 5.0 device but in eVC4.0 workspace no debugging activity is being perform.

  Please suggest, if i am missing any step.

  Note: I have found many links that point out that eVC4.0 application can not be debuged on WinMobile5.0 device. Is it true

  Thanks in advance.

  Regards,

  Ram

  
  

• Usman Sheikh

  Hi Avinash,

  ://forums.microsoft.com/MSDN/ShowPost.aspx PostID=210095&SiteID=1 says about soft reset(using ExitWindowsEx). I am looking hard reset.

  Thanks,

  Ram

  
  

• gheese

  Hi Ram,
  Once you launch the eVC4.0 application through VS2005 using dummy project, you won't be seeing it debugged under eVC4.0. You will be seeing it debugged under VS2005 because you launched the application using VS2005.

  Before doing F5, please do the following in VS2005 IDE

  • Please open the source file corresponding to fld_link.exe using VS2005
  • Please load the symbols corresponding to fld_link.exe in tools->Options->Debugging->Symbols
  • Now press F10/F11. If you are doing F5 then put some Breakpoint in the source file

  You should be seeing the yellow pointer at start of app.

  BTW one basic question about your application. What is the target of the application which you created and built in terms of architecture(ARM, X86, SH4 or MIPS) and WinCE version

  Regards
  Gaurav

  
  

• Big Kahuna

  As Jeff said, first check whether you are able to manually launch the application to test for any missing dependency. Following blog will help you out in debugging eVC++ 4.0 applicaqtion using VS2005 http://blogs.msdn.com/vsdteam/archive/2006/02/05/525224.aspx

  Regards
  Gaurav

  
  

• carina9138

  Hi Gaurav,

  I conclude from your post that it is not possible to debug an application whose debug build is prepared in eVC4.0 IDE on Windows Mobile 5.0. I was using the workaround by setting the remote executable to debug as my eVC executable in VS2005, however you say that the eVC workspace should be opened and re-built in VS2005 itself before debugging. Please correct if my understanding is wrong.

  To answer your questions, the eVC application is built for the following:

  Target Procesor: ARM

  WinCE version: WinCE4.2

  Thanks & Regards,

  Ram

  
  

• Scott Kirk

  Hi,
  First issue:
  Any system API that isn't supported on new platfroms ie WM 5.0 shall fail. And your eVC code/binary must be ready to handle that case.
  
  Second isssue:
  Did you take a look at http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=210095&SiteID=1.
  
  Thanks
  
  
  
  

• Rajesh Chandrashekaran

  The device folks might be able to help.

  Thanks,

  Ayman Shoukry

  VC++ Team

  
  
  

• GHR

  Hi Gaurav,

  1. I performed steps 4 and 5.

  2. On pressing F10/F11 or F5, I am getting compilation errors in VS2005. Removal of these errors is equivalent to migrating eVC++4.0 to VS2005 but I don't want to migrate eVC++4.0 code to VS2005. Is removal of these errors equivalent to migrating eVC++4.0 to VS2005

  thanks,

  Ram

  
  

• J-Thread

  If you just copy the project over and start it manually, does it work It's possible that you're missing a dependency, and this test should reveal that. What macro are you using to specify the target directory I'd be inclined to not use a macro, and use the fully qualified filename instead, because there's less to go wrong. Hope this helps,

  Jeff

  
  
  

• robbe_15

  Hi Ram,

  First of all I hope that in step 4 you didn't open the complete eVC4.0 project using VS2005. In step 4 please open the cpp file (file containing entry to code..I mean main) only using File->Open->File

  Before pressing F5 please clean the solution. On pressing F5, dialogue will popup asking you 'Would you like to build it'. Please press No button

  Let me know if you are able to debug it.

  Regards
  Gaurav

  
  
• Debugging of eVC++ 4.0 application on WinMobile 5.0 using VS2005 dummy project