e_petersen
13 years agoNew Contributor
AQtime with C++ Builder XE - No result window
Hi.
I tried to use AQtime shipped with C++ Builder XE Professional, and ran into a problem. The sample projects work just fine and even on a newly created project everything is fine - but when I try to profile *my* application I just don't get any result-window. I start the application using "Run with Profiling", the normal usual dialogs appear - but after application-exit there are no results (I made sure that the application really is terminated).
I tried to isolate the cause for this by stripping down the application and came to a point where after I removed a call to one of our DLLs the result-window reappeared. Just adding a call to a function in this DLL (and thus binding it to the application) makes the result-window not show up at program termination. Please note that it is not necessary to actually execute that function call - loading the DLL is enough. I figure it must have something to do with static objects in this DLL (which get constructed when loading the DLL and destroyed before unloading it).
Can you offer me any kind of explanation what could cause this and what to do about it?
Thanks you.
Best Regards
Eike Petersen
I tried to use AQtime shipped with C++ Builder XE Professional, and ran into a problem. The sample projects work just fine and even on a newly created project everything is fine - but when I try to profile *my* application I just don't get any result-window. I start the application using "Run with Profiling", the normal usual dialogs appear - but after application-exit there are no results (I made sure that the application really is terminated).
I tried to isolate the cause for this by stripping down the application and came to a point where after I removed a call to one of our DLLs the result-window reappeared. Just adding a call to a function in this DLL (and thus binding it to the application) makes the result-window not show up at program termination. Please note that it is not necessary to actually execute that function call - loading the DLL is enough. I figure it must have something to do with static objects in this DLL (which get constructed when loading the DLL and destroyed before unloading it).
Can you offer me any kind of explanation what could cause this and what to do about it?
Thanks you.
Best Regards
Eike Petersen