Troubleshooting
ARM DUI 0482K Copyright © 2010-2012 ARM. All rights reserved. 14-3
ID120712 Non-Confidential
14.2 Report issues
If the data in your reports seems incomplete, you might not have included a compilation option
essential to Streamline. Common report problems and solutions are:
Symptom Streamline does not show any source code in the Code view.
Solution: Make sure that you used the
-g
option during compilation. Streamline
must have debug symbols turned on to match instructions to source code.
Symptom Streamline does not show source code for shared libraries.
Solution: Add the libraries using the Capture options dialog box. Click Add
Image... in the images section, navigate to your shared library, and then add it.
Symptom The data in the call paths view is flat. The presented table is a list, rather than a
hierarchy.
Solution: Use the
-fno-omit-frame-pointer
and
-marm
options during compilation
and be sure to check the Call Stack Unwinding option in the capture options
dialog box.
Streamline does not walk the stack for kernels, loadable kernel modules, or
statically linked drivers. These generate flat data in the call paths view.
Symptom Functions that you know are highly used are missing from the reports. Other
functions might seem artificially large.
Solution: This can be because of code inlining done by the compiler. To turn
inlining off, add
-fno-inline
as an option during compilation.
Symptom A newly-generated analysis report has no data.
If you experience this and the profiling session had event-based samling enabled,
the PMU on your target might not have triggered the interrupts correctly. Test on
alternate hardware or disable event-based sampling in the counter configuration
dialog box.
14.2.1 See also
Reference
• Target connection issues on page 14-2.
To Previous Page
Loading...
