locked
function name and process name become !(null) on AppVerifier's log. RRS feed

  • Question

  • function name and process name become !(null) at AppVerifier's log.
    but  when do doube free on purpose, function name and process name become appropriately name.

    Isn't AppVerifier bug

    I want to know a appropriate way.
     -  Should we need to double  free on purpose to draw function name?
     -  Should we avoid this problem to use another appropriate  way?



    for exsample. this state is caused by following code 
    >>
    >> GetDC(g_hWnd)
    >> /*don't call ReleaseDC */
    >> ---------------- result ---------------------------------------------------------------
    >> # DESCRIPTION END
    >>| shim_usergdi.dll 19 | 1 nk.exe 88037914'Callstack:
    >>| shim_usergdi.dll 19 | 1 nk.exe 88037914'   0x217f29d8: shim_usergdi.dll!(null) + 29d8h
    >>| shim_usergdi.dll 19 | 1 nk.exe 88037914'   0x20011058: !(null) + 11058h
    >>| shim_usergdi.dll 19 | 1 nk.exe 88037914'   0x2001199c: !(null) + 1199ch
    >>| shim_usergdi.dll 19 | 1 nk.exe 88037914'   0x03f67760: coredll.dll!(null) + 1d760h
    >>| shim_usergdi.dll 19 | 1 nk.exe 88037914'Leaked items:
    >>| shim_usergdi.dll 19 | 1 nk.exe 88037914'   0x003a0583   (GetDC) (checkpoint: 0)

    function name and process name become appropriately name , when do doube free on purpose.
    >>{
    >>int *p;
    >>p = (int*)malloc(sizeof(int));
    >>free(p);
    >>free(p);
    >>}
    >>GetDC(g_hWnd);
    >> /*don't call ReleaseDC */
    >> ---------------- result ---------------------------------------------------------------
    >># DESCRIPTION END
    >>| shim_usergdi.dll 20 | 1 nk.exe 88037914'Callstack:
    >>| shim_usergdi.dll 20 | 1 nk.exe 88037914'   0x217e29d8: shim_usergdi.dll!(null) + 29d8h
    >>| shim_usergdi.dll 20 | 1 nk.exe 88037914'   0x2001107c: test01.exe!WinMain + 7ch
    >>| shim_usergdi.dll 20 | 1 nk.exe 88037914'   0x200119e0: test01.exe!WinMainCRTStartup + 34h
    >>| shim_usergdi.dll 20 | 1 nk.exe 88037914'   0x03f67760: coredll.dll!(null) + 1d760h
    >>| shim_usergdi.dll 20 | 1 nk.exe 88037914'Leaked items:
    >>| shim_usergdi.dll 20 | 1 nk.exe 88037914'   0x03a005bd   (GetDC) (checkpoint: 0) 


    [PS]
    - setting
      Test setting: HEAP Verifier is checked.
      Handle Leak Tracker is checked. 
      Shell Verifier is checked.

    -version
     Microsoft Window CE Test Kit version 5.00
     Application Verifier Tool for Windows Mobile® 5.0
     (http://www.microsoft.com/downloads/details.aspx?familyid=d275348a-d937-4d88-ae25-28702c78748d&displaylang=en)

    Thanks.

    Sunday, October 4, 2009 1:09 PM

All replies

  • Hello,

    Create Release Directory either at device root or in ur application folder (i.e \Program Files\xyz\Release )and copy map file in that. you will start getting stack trace.

    Thanks
    Arpit Pradhan
    WinCE CODER (If you think my solution help you in some sense do mark my Reply as Answer)
    Monday, October 5, 2009 5:40 AM
  • Thanks for  Replay.
    But, I created Release Directory. and  copied  \test01.exe  \Release\test01.map.
    then function name and process name become !(null) at AppVerifier's log.

    Thanks.

     
    Monday, October 5, 2009 6:45 AM