When your application is profiled by AQTime, the Event View panel traces all exceptions that occur in the application (to enable the tracing, activate the Common > Exceptions > Active panel option).

When an exception occurs, examine the Event View panel to view information about the exception code and the exception description.
If the panel’s Show call stack option is enabled, you can examine the exception’s call stack displayed in the Event View. The topmost routine is the one where the exception occurred.
If the application was compiled with debug information, you can view the source code of a routine listed in the call stack. To do this, double-click this routine and then switch to the Editor panel (the path to the source files must be specified in the Project Search Directories and Search Directory dialogs).

To view the source code of a routine listed in the call stack, double-click this routine to switch to Visual Studio’s Code Editor that displays the routine’s source code.

To view the source code of a routine listed in the call stack, double-click this routine to switch to Embarcadero RAD Studio’s Editor panel that displays the routine’s source code.
To determine the cause of the problem, you can generate a dump file that includes information about the application’s memory, threads, loaded modules and other data that may help you understand what went wrong. You can also configure AQTime so that it generates dumps automatically. See Generating Dumps for Profiled Applications.

Note:

AQTime does not support profiling of .NET applications that reside on another computer. Profiling of these applications causes an exception that occurs within the application code due to security peculiarities of the .NET Framework (see Profiling .NET Applications - Specifics).

Find the Routine Where an Exception Occurred

See Also