Contributions
Re: AQtime 8.24 cannot see functions in my 64-bit DLL built with C++ Builder XE4
Hi Alex, I have been working with the AQtime support staff on this issue, and we covered the topics you noted (thank you). The "View by" combobox on the Setup panel had been set to "Source File", which they had me change to "Default". That enabled the display/access to all of the routines in all of the units of the project. Kathleen9 years agoPlace AQtime QuestionsAQtime Questions5.8KViews2likes1CommentAQtime 8.24 cannot see functions in my 64-bit DLL built with C++ Builder XE4
This DLL is written in Standard C++ (C++11). I can successfully profile it when built for 32-bit. Attachment 64_bit.bmp shows how AQtime sees my 64-bit DLL... only a tiny subset of the functions that are in the library. Attachment 32_bit.bmp shows how AQtime sees the 32-bit files; all of the functions are seen. Other than the "bitness", these were built with the same instructions. Both are debug builds. The reason I upgraded to AQtime v8.24 from v8.10 is that v8.10 had technical problems supporting 64-bit apps built with RAD Studio XE4 (according to emails from SmartBear techs in January 2014). I don't know whether this issue is likewise a technical problem, or if there are additional steps I need to take when building my DLL for profiling as 64-bit. Either way, I am requesting help with this matter. Thanks, KathleenSolved9 years agoPlace AQtime QuestionsAQtime Questions5.8KViews0likes3CommentsRe: Uninstrumented routines, Duplicate code, C++ Builder XE4
Hi Alex, I believe the problem is with AQtime, XE4 and 64-bit applications. Something about how XE4 creates the assembly code (I couldn't view it in the Disassembly panel because of the Duplicate Code error... Catch-22). My OS is Win7-64, and I keep all Microsoft patches up-to-date. Kathleen11 years agoPlace AQtime QuestionsAQtime Questions5.4KViews0likes0CommentsRe: Uninstrumented routines, Duplicate code, C++ Builder XE4
To update anybody who may be reading this thread, Jay noted that I was profiling a C++ Builder XE4 GUI application compiled for 64-bit. He suggested I try building it as 32-bit and see if that made a difference. It did. Not only did the warnings about duplicate code go away, but AQtime was able to open my executable instantly; the 64-bit build takes upwards of ten minutes to analyze upon opening.11 years agoPlace AQtime QuestionsAQtime Questions5.4KViews1like0CommentsRe: Uninstrumented routines, Duplicate code, C++ Builder XE4
Unfortunately, whatever is causing this affects all of my forms. I'm hoping to hear it's something about declarations... such as "carry the 'virtual' down to the derived classes".11 years agoPlace AQtime QuestionsAQtime Questions5.4KViews0likes0CommentsUninstrumented routines, Duplicate code, C++ Builder XE4
When I run a Performance profiler on my VCL GUI application, the Uninstrumented Routines dialog reports that all of my forms that derive from base forms contain Duplicated Code. How can I find out which code is triggering this condition in the profiler? The help pages explain a compiler setting for Visual Studio, but unfortunately I don't know how to translate that information into something that might correspond in C++ Builder XE4. Thanks for your help. KathleenSolved11 years agoPlace AQtime QuestionsAQtime Questions9.3KViews0likes9CommentsHow do I find out what is unsafe about my code?
Performance profiler, C++ Builder XE4 GUI app. The Uninstrumented Routines identify several of my selected routines as "Unsafe code". The help file suggests this might be caused by using string literals in parameters to VCL function calls, or in any assignments. Am I to understand that I must assign string literals to AnsiString instances and use those to assign the values to anything VCL? That would really clutter the code something awful. I'll stop speculating... somebody please help me to understand! Thanks, Kathleen11 years agoPlace AQtime QuestionsAQtime Questions4.8KViews0likes1CommentDisabling dynamic CPU frequency mode
When I run the Performance profiler on my C++ Builder XE4 executable, I get a dialog that says: Your processor supports the SpeedStep technology. We recommend that you disable the dynamic CPU frequency mode, because the timing results may be inaccurate if this mode is active. Continue profiling? My questions: 1. How do I disable the CPU frequency mode? 2. What other features of my computer may cause me to regret disabling this mode? I am answering "Yes" to the "Continue profiling?" question, and I get results... is it a big deal if I just accept the warning and ignore it?Solved11 years agoPlace AQtime QuestionsAQtime Questions14KViews0likes2CommentsRe: C++ Builder XE4: Unable to open file AQTIME8BDS11.LIB
Update: I rebuilt my project from scratch (i.e., started a new C++ Builder XE4 VCL Forms project and imported all of the source files from my "real" project) and was able to get it to build and run sans AQTime. I don't know what may have gone wrong with my old project, but am saving the project files for a little while in case they are useful for attempts to debug this. Thanks in advance for any suggestions you may have. Kathleen11 years agoPlace AQtime QuestionsAQtime Questions2KViews0likes0Comments