The profiling should have nothing to do with your app because sample data is collected from kernel mode driver.
What problem do you have when you profile an app with QT? Is the environment configured correctly?
well when I try to launch our application with the code analyst from within Visual Studio I get an error message reporting that the injection failed. When I was browsing the web for a solution I found a readme file from Code analyst stating that QT 4 is not supported and that QT 3 would be needed. In the current readme file I didn't find that hint - maybe there is no problem left with QT in general.
In general code anaylst seems to run OK because we 2were able to run the profile against DLLs which used QT themselves but no GUI etc.
Because the first results from code analyst were very helping we'd like to find a way to make it run with our application.
Currently CodeAnalyst is using QT 4.3.0 on Windows. We are still loading that version of QT in our Visual Studio integrated package. Can you specify the working directory for your launched application such that it can directly find the required QT dlls, rather than relying on the PATH environmental variable to find them?
If you're also testing an integrated package in Visual Studio, I can see how the conflicting QT 4 libraries with the same name might have issues. In that case, it would probably be easiest to prevent the CodeAnalyst integrated package from loading and do your profiling from the stand-alone gui.
I hope this helps.
specifying the working directory would be tricky because there are other files that are currently reached through the working directory and they aren't in the QT directory. Maybe the profiling from the stand alone GUI will solve the problem - we'll give it a try.