The IDE can import session data generated by a performance-measuring tool while an application ran. This allows you to view the results of previous analyses, including those shared by other team members or those from sessions that you ran outside of the IDE.
For some development environments, it might not be possible to start an analysis session from the IDE. For example, if the host and target machines aren't connected to the same network, or if you don't have qconn or a similar target service to forward session data to the host.
In these cases, you can run an instrumented binary from the command line, copy the profiling results to your host, then import them into the IDE to view the application's call counts and function runtimes. This workflow is known as a postmortem analysis.
You can also create an Application Profiler session by importing a kernel event log (.kev) file. The new session contains the profiling results generated by an instrumented application binary that ran during the kernel event trace. Details about importing this type of profiling data as well as data generated by other supported methods are given in the next section.
For Valgrind Cachegrind, you can import a text file containing the results of a previous cache usage analysis by following the procedure given in “Importing Valgrind logs”.