Hi Hans,
I've consulted with our developers, and below, there are the things I could find out:
* Most likely, the C0000026 exception is raised by your application (that is why you failed to reproduce the behavior without AQtime integration). The problem is that AQtime shouldn't catch such exceptions.
* So, to help us investigate the problem, please follow the steps below:
1. Start AQtime with the -NotOpenApp command-line argument. For example, you can use the following command line:
"c:\Program Files\SmartBear\AQtime 7\Bin\AQtime.exe" -NotOpenApp
2. Select the 'File | Open...' main menu item.
3. In the Open File dialog, select the executable file of the RAD studio and click Open.
4. Select the "Tracing | Exception Trace Profiler" profiler.
5. Click the Run toolbar button (the green arrow) or press F5 to start the profiling.
6. AQtime will start the IDE.
7. Perform all the described actions before loading the DB plug-in package.
8. Select the "Options | Options..." main menu command - the Options dialog will appear.
9. Enable the "Profiling Time | Event View | Debug Events | Generate dump on exception" option and specify a dump folder.
10. Set the "Profiling Time | Event View | General | Exceptions | Depth shown" setting to 100 and click OK.
11. Load the DB plug-in package and AQtime will generate dump files for all exceptions that will occur in the application until it is closed.
12. After the problem occurs, right-click somewhere within the Event View panel (it is opened by default at the bottom of AQtime's window) and select the 'Save All...' item.
13. Save the panel's contents to an HTML file and send the file along with all of the generated dump files to our Support Team via the Contact Support form.
Thanks in advance.
