When optimization is turned on, the relationship between line numbers and compiled code is not clear. This affects the accuracy of the TD32 debugging information that TestComplete uses. To ensure that debugging information is as accurate as possible, SmartBear recommends disabling optimization.
Optimization should not affect the behavior of your program at runtime. (If so, then you either rely on undefined behavior or you find an error in the optimizer. Suppose the former until you can prove the latter.)
source share