Finding the cause of a Data Abort or Crash

If you’re looking for the reason of a data abort or an exception which occurs during application execution on CE 5.0 or 6.0.
Then take a deep look into Bruce Eitman’s following blog entries (http://geekswithblogs.net/BruceEitman/archive/2008/05/19/windows-ce--finding-the-cause-of-a-data-abort.aspx and http://geekswithblogs.net/BruceEitman/archive/2008/06/02/platform-builder-find-the-source-of-a-data-abort-an.aspx).
They provide a very simple explanation about usage of MAP and COD files for crash investigation on Windows CE based systems.

Another useful source about this is the following article:
http://codeproject.com/KB/debug/mapfile.aspx

Creation of MAP files with Platform Builder depends on the value of the WINCEMAP macro in your SOURCES files. With IDE you should set the “\Fm” linker option.
For creation of COD files with PB set the environment variable WINCECOD to 1 and rebuild. When using IDE (e.g. Visual Studio) you should add the compiler option “\FAcs” or set the correct entry in the IDE (C/C++ --> Listing file type --> Assembly, Machine Code, and Source).