Forum Discussion
Hi,
Thank you a lot for the detailed description of your actions and sorry for not replying earlier.
My guess is that AQTime was unable to access (debug?) version of some module and this prevented profiler from been able to function.
I believe that you followed the steps described in the documentation (https://support.smartbear.com/aqtime/docs/profiling-with/prepare-apps/compiler-settings-native/delphi/delphi-7.html).
Especially I am thinking about this note:
"If you want to keep Build with runtime packages (for instance to control exe size), you can still use the Allocation profiler. When you include your application in an AQTime project, you will also have to include the <Windows>\System32\VCLnn.BPL or <Windows>\System32\RTLnn.BPL file, [...]".
Also, SmartBear provides a really good technical assistance, so I would recommend to create Support ticket via the https://support.smartbear.com/message/?prod=AQtime form, reference this thread and ask for their recommendations.
Hi Alex,
Thanks for your response, yeah its all a bit strange but seems to be working ok for now. unfortunately we must use the runtime packages as this legacy system has its own list of custom packages/bpl's of which there are several hundred so compiling into a standalone exe isn't really an option unfortunately.
we would also love to migrate to a more modern iteration of Delphi but again all the third party libraries and stuff are well embedded and some obsolete so the time required to update these etc.. would be more then its worth
In the meantime if I encounter any more issues I'll update this thread and maybe open a ticket if required.
thanks again
Phil
Related Content
- 7 years ago
- 5 years ago
Recent Discussions
- 4 months ago
- 2 years ago