Browse your file system, and select the images and libraries you want to profile.
When compiling images on your host, ensure that you use the -g compiler option to enable debug symbols.
To improve the call path quality, disable inlining with the -fno-inline compiler option.
Note
For more information on compiling your application, see the Compile your application or the Compile your application.
In the Start view, click Capture Settings.
In the Program Images section, control symbol loading for the ELF images, executables, or APK listed:
Note
If you compiled your application for multiple architectures, you must unzip the :file: app-debug.apk to see the :file: .so files in Program Images.
Select Use all images for analysis or Use none of the images for analysis.
To browse your file system and choose an image executable or APK, click Add image, select the required file, then click Open.
Note
If you select an image with the extracted debug information and CFI on this step, Streamline does not show the disassembly of this image.
Streamline relies on executable code to generate accurate callpath information. Arm recommends that you always provide complete ELF images for analysis.
To select a separate file containing the extracted debug information and CFI, click Select separate debug image.
Note
This option is available when the Debug Info or CFI column displays the
icon.
To remove the selected entries, click Remove.
In the Program Images table, select the checkbox in the Use column for each image you want to include in the analysis.
Click Save.
Note
These images can be changed when you re-analyze the stored capture.
The images you selected in the Program Images table are now ready for profiling.
See Download process images for more information about the image download functionality, which is an alternative to manually selecting images and libraries on the host in the Program Images section.