Different behaviour when profiling

Hi Dave,

This can be a memory-related issue caused by the fact that AQtime changes the profiled application when instrumenting its code. If there are some problems with pointers in your application, this can result in a behavior change. Could you please provide us with a simple sample with which the problem can be reproduced?

BTW, as a workaround, you can try excluding the problematic function from profiling (see the "Controlling what to profile" help topic ( http://www.automatedqa.com/support/viewarticle.aspx?aid=17905 ) for more information).