none
How to debug DataAbort of CoreDll.dll? RRS feed

  • Question

  • I use print output log in a process of DumpRenderTree.exe, likes:

       ......

       printf("Log1\n");    // this first print

       printf("Log2\n");

       .....

    but first line "printf("Log1\n"); " is OK, and 2nd line code "printf("Log2\n");" is failed. the the following is log:

    =============================================================================

    PID:106D006E TID:11970072 PID:106D006E TID:11970072 Exception 'Data Abort' (0x4): Thread-Id=11970072(pth=c0c2ace8), Proc-Id=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe', VM-active=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe'
    PC=4006b1d4(coredll.dll+0x0005b1d4) RA=4006b038(coredll.dll+0x0005b038) SP=0017d344, BVA=000003c4
    PID:106D006E TID:11970072 PID:106D006E TID:11970072 Exception 'Data Abort' (0x4): Thread-Id=11970072(pth=c0c2ace8), Proc-Id=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe', VM-active=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe'
    PC=4006b1d4(coredll.dll+0x0005b1d4) RA=4006b038(coredll.dll+0x0005b038) SP=0017cd04, BVA=000013c3
    PID:106D006E TID:11970072 PID:106D006E TID:11970072 Exception 'Data Abort' (0x4): Thread-Id=11970072(pth=c0c2ace8), Proc-Id=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe', VM-active=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe'
    PC=4006b1d4(coredll.dll+0x0005b1d4) RA=4006b038(coredll.dll+0x0005b038) SP=0017c6c4, BVA=000013c3
    PID:106D006E TID:11970072 PID:106D006E TID:11970072 Exception 'Data Abort' (0x4): Thread-Id=11970072(pth=c0c2ace8), Proc-Id=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe', VM-active=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe'
    PC=4006b1d4(coredll.dll+0x0005b1d4) RA=4006b038(coredll.dll+0x0005b038) SP=0017c084, BVA=000013c3
    PID:106D006E TID:11970072 PID:106D006E TID:11970072 Exception 'Data Abort' (0x4): Thread-Id=11970072(pth=c0c2ace8), Proc-Id=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe', VM-active=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe'
    PC=4006b1d4(coredll.dll+0x0005b1d4) RA=4006b038(coredll.dll+0x0005b038) SP=0017ba44, BVA=000013c3
    PID:106D006E TID:11970072 PID:106D006E TID:11970072 Exception 'Data Abort' (0x4): Thread-Id=11970072(pth=c0c2ace8), Proc-Id=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe', VM-active=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe'
    PC=4006b1d4(coredll.dll+0x0005b1d4) RA=4006b038(coredll.dll+0x0005b038) SP=0017b404, BVA=000013c3
    PID:106D006E TID:11970072 PID:106D006E TID:11970072 Exception 'Data Abort' (0x4): Thread-Id=11970072(pth=c0c2ace8), Proc-Id=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe', VM-active=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe'
    PC=4006b1d4(coredll.dll+0x0005b1d4) RA=4006b038(coredll.dll+0x0005b038) SP=0017adc4, BVA=000013c3
    PID:106D006E TID:11970072 PID:106D006E TID:11970072 Exception 'Data Abort' (0x4): Thread-Id=11970072(pth=c0c2ace8), Proc-Id=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe', VM-active=106d006e(pprc=c0c2a1c4) 'DumpRenderTree.exe'
    PC=4006b1d4(coredll.dll+0x0005b1d4) RA=4006b038(coredll.dll+0x0005b038) SP=0017a784, BVA=000013c3

    So, my question is how to debug this issue?

    Old NTG5HUH device is OK. and I can't get information about modifying of new device or system software. and I got a old k.coredll.map file.

     k.coredll

     Timestamp is df2b99ab                          

     Preferred load address is 10000000

    ..............

     0001:00059f1c       _real_flsbuf2              1005af1c f   k.coredll_ALL:_filbuf.obj

     0001:0005a0ac       UnhandledExceptionFilter   1005b0ac f   k.coredll_ALL:unhandled.obj
     0001:0005a128       __C_ExecuteExceptionFilter 1005b128     k.coredll_ALL:jmpuwind.obj
     0001:0005a128       __C_ExecuteTerminationHandler 1005b128 f   k.coredll_ALL:jmpuwind.obj
     0001:0005a168       __raise_int_divide_by_zero 1005b168 f   k.coredll_ALL:diverr.obj

    And I got location is in function __C_ExecuteTerminationHandler <by PC=4006b1d4(coredll.dll+0x0005b1d4)> and called < by RA=4006b038(coredll.dll+0x0005b038)>


    Jerry.Liu SDET


    Monday, August 12, 2013 9:13 AM

All replies