Windows CE 6.0 R3 Data Abort on ARM processor - no module name in exception report; only "???" RRS feed

  • Question

  • I'm trying to sort out why I do not see a module name in the following Data Abort report I'm getting from a Win32 program running on an ARM processor on my device. Everything I've seen online shows a module name. I have PDB files, MAP files and COD files for all my code, so I'm fearful that the "???" actually represents some sort of OS-level DLL/module, and that's why I don't have better information. If that is the case, is there a way to figure out what the routine that's failing might be if I cannot get OS MAP files from the device vendor?

    Exception 'Data Abort' (4): Thread-Id=09160006(pth=882c5438), Proc-Id=09150006(pprc=882c5e14) 'mypgm.exe', VM-active=09150006(pprc=882c5e14) 'mypgm.exe'
    PC=00220178(???+0x00220178) RA=013e5ae1(???+0x013e5ae1) SP=0003ecc8, BVA=f9c836d9
    KPSLExceptionHandler: flags=1 ControlPc=c0036cb8
    Exception 'Raised Exception' (-1): Thread-Id=09160006(pth=882c5438), Proc-Id=00400002(pprc=82ef3310) 'NK.EXE', VM-active=09150006(pprc=882c5e14) 'mypgm.exe'
    PC=c003bb84(k.coredll.dll+0x0001bb84) RA=8112875c(kernel.dll+0x0000775c) SP=d449f1f4, BVA=ffffffff

    Friday, October 21, 2016 1:56 PM


  • Just have a look at, find the function that has code at 0x1Ab84 (subtract 1000h from the address) and you will find the function that caused the data abort (almost 100% likley due to you passing a bad pointer to it).

    This is as much info as you get most of the times. Call stack is obviously trashed.

    Good luck,

    Michel Verhagen, eMVP
    Check out my blog:

    Microsoft Embedded Partner
    NXP Proven Partner
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here:

    Friday, October 21, 2016 7:31 PM

All replies