Ask a Question

Allow "Unsafe" code to be profiled, by allowing them "by hand"

0 Kudos

Allow "Unsafe" code to be profiled, by allowing them "by hand"

Currently, using Delphi 64bit generated code the AS operator as well as for loops with constant integers generate code that is detected by AQTime as unsafe.


Nevertheless I want to be able to profile this code, or at least allow it to fire some trigger.


So the idea is to allow these "unsafe" routines to be "forcibly" instrumented by adding them in your project as "ignore unsafe" routines.

Regular Visitor

Related to Case #00155347

Occasional Visitor

This seems to have been fixed in the 8.60 Version ( )


"Fixed: AQtime could mistakenly recognize 64-bit Delphi applications’ routines that contain exception-handing and typecasting code as unsafe. "

Welcome to the AQTime Feature Requests board!

Here you can review submitted feature requests and vote up the ones you like! If you can't find the feature you want - go ahead and suggest your own idea. Ideas with the highest rating can be implemented in the product.

Check out the Create a Feature Request guide for more information.
New Here?
Welcome to the Community
Sign Up Here