To analyze a profile database generated using CLI, click to go to the Import Profile Session. The following screen is displayed:
Figure 1. Import Session – Importing Profile Database
This can be used to import the processed profile data collected using the CLI or the processed profile data saved in GUI’s profile session storage path. You must do the following:
- Specify the path containing the session.uprof file in the Profile Data File box.
- Binary Path: If the profile run is performed in a system and the corresponding raw profile data is imported in another system, you must specify the path(s) in which binary files can be located.
- Source Path: Specify the source path(s) from where the sources files can be located. No sub- directories will be searched in this path to locate any source files.
-
Root Path to Sources: Specify the path to the root of
multiple source directories. The entire directory and sub-directories present in
that path will be searched to locate any source files.Note: The search might take time as all the sub-directories will be searched recursively.
- Force Database Regeneration: To forcefully regenerate the database file while importing.
- Use Cached Source/Binary/Symbol Files: Enable this option to reuse cached source, binary, and symbol files.