Topic
  • 2 replies
  • Latest Post - ‏2013-08-19T23:24:11Z by Dongxi Jin
4E91_Lance
4E91_Lance
2 Posts

Pinned topic EXU: Unhandled exception in _clean_type_info_names_internal

‏2013-05-17T15:53:42Z |

I'm trying to use PurifyPlus 7.0.1.0-003 on Win7 x86 to instrument one of our native C++ apps built with VS 2010.  It starts main, then these errors:

[I] Starting main
[I] EXI: Ignored exception in _clean_type_info_names_internal {2 occurrences}
        Exception code: 0xc0000005 [Error: access violation reading from 0xffffffff]


        Exception address:  [C:\WINDOWS\SYSTEM32\MSVCR100.DLL ip=0x58AD2AD5]
[E] EXU: Unhandled exception in _clean_type_info_names_internal {1 occurrence}
        Exception code: 0xc0000005 [Error: access violation reading from 0xffffffff]
        Exception address:  [C:\WINDOWS\SYSTEM32\MSVCR100.DLL ip=0x58AD2AD5]
        Filter:  [C:\Program Files\IBM\RationalPurifyPlus\PURERT.DLL ip=0x3F0026D0]
        Exception location
             [c:\WINDOWS\SYSTEM32\MSVCR100.DLL ip=0x58AD2AD7]

Then terminates the app.   I've searched the documentation, but no mention of this type of error.

Any suggestions?

Thanks,

-Lance

 

  • Lances
    Lances
    1 Post

    Re: EXU: Unhandled exception in _clean_type_info_names_internal

    ‏2013-08-16T20:49:29Z  

    After filing a PMR and getting help from IBM support,  the resolution was to not instrument the C++ runtime library, so additional options needed for pre-instrumentation of the exe were:

    -purify-exclude-must="C:\WINDOWS\SYSTEM32\MSVCR100.DLL"  -allow_setwindowshook

    -Lance

     

  • Dongxi Jin
    Dongxi Jin
    27 Posts

    Re: EXU: Unhandled exception in _clean_type_info_names_internal

    ‏2013-08-19T23:24:11Z  

    Hello Lances,

    Did you try to use the debug version of runtime library to build your application as mentioned in the technote "Running a program instrumented with Purify results in _clean_type_info_names_internal crash"?

    Regards,