The Failure Emulator profiler lets you emulate various application failures and check how your application handles them. If your application fails under emulated conditions, you may want to modify its source code to prevent such failures in the future.

To find a specific place in the application’s source code that caused your application to fail, do the following:

Set the application failures you want to emulate and start profiling.
Perform actions that can cause a failure and get the profiling results.
Analyze the profiling results and find the routine that caused your application to fail:
- All the failures that were simulated while profiling the application are shown in the Report panel. Select the desired failure in the Report panel and switch to the Details panel.
- The Failure Stack pane of the Details panel shows the call stack that caused the failure. The topmost routine in the stack is a system function where the error occurred.
  
  Go through the rows of the pane from top to bottom until you find the first routine that belongs to your application (the file specified in the Source File column must contain some or the entire source code of your application).
- Double-click the found routine in the Details panel and switch to the Editor panel (the path to your application's source files must be specified in the Project Search Directories or Search Directories dialog)Code Editor page that displays the application's source codeRAD Studio Editor’s page that displays the application's source code. AQTime automatically highlights the routine where the error occurred.
  
  If the application was profiled at line level, AQTime highlights the line where the error occurred.

Find Routines That Fail Under Specific Conditions

See Also