Critical error detected c0000374
Hi, we bought AQTime 6.5 to profile an MFC C++ 32-bit application compiled with Visual Studio and running under Win7. AQTime won't start our application. It just stops with the message "Critical e...
Forum Discussion
Hi again,
AQTime is a very nice product, when it works. But there's one ting that I find strange: when you run our application with AQTime - up pops a message dialog saying that some routines could not be instrumented because of "Unsafe code". Fine, I'm an assembly language programmer but I haven't taken the time to investigate what is meant with "Unsafe" -- but what makes me worried is the fact that the number of routines that are considered "Unsafe" differ between each run - even though nothing changes in the exe. This kind of pattern tells me that there is something uninitialized in AQTime - otherwise it couldn't produce unpredictable results - it should be the same behaviour every time.
I don't know how to proceed with AQTime 6.5?
AQTime is a very nice product, when it works. But there's one ting that I find strange: when you run our application with AQTime - up pops a message dialog saying that some routines could not be instrumented because of "Unsafe code". Fine, I'm an assembly language programmer but I haven't taken the time to investigate what is meant with "Unsafe" -- but what makes me worried is the fact that the number of routines that are considered "Unsafe" differ between each run - even though nothing changes in the exe. This kind of pattern tells me that there is something uninitialized in AQTime - otherwise it couldn't produce unpredictable results - it should be the same behaviour every time.
I don't know how to proceed with AQTime 6.5?
