If you successfully complete a capture session but have a problem with the resulting report data, consult this list of common issues.
| Problem | Solution |
|---|---|
| Streamline does not show any source code in the Code view. | Make sure that you use the If necessary, ensure that the path prefix substitutions are set correctly. See the Path Prefix Substitutions dialog box in the Code view. |
| Streamline does not show source code for shared libraries. | Add the libraries using the Capture Settings dialog box.
|
| The data in the Call Paths view is flat. The presented table is a list rather than a hierarchy. | Use the GCC options If frame pointers are set correctly, the disassembly of the code contains instructions in the form
Note
|
| Functions that you know are highly used are missing from the reports. Other functions might seem artificially large. | This problem can be because of code inlining that is done by the compiler. To turn inlining off, add Also, check that your debug symbols are correct. |
If you still need help with your capture, send the gator-log.txt file, along with your capture, to the support team. The log file is in the same directory as the capture, and is available after the capture has finished. It records basic debugging and support information, such as errors, warnings, and information about the device.
If you are using Streamline as part of Arm Development Studio, open an Arm Support case.
If you are using Streamline as part of Arm Performance Studio, contact Arm at performancestudio@arm.com.
To create a gator-log.txt file for a local capture, enable the --capture-log command line option.