You copied the Doc URL to your clipboard.

Troubleshooting report issues

If you successfully complete a capture session, but have a problem with the resulting report data, consult the following list of common issues.

Each common problem is listed wit a possible solution:

Problem

Solution

Streamline does not show any source code in the Code view.

Make sure that you used the -g option during compilation. Streamline must have debug symbols turned on to match instructions to source code.

Streamline does not show source code for shared libraries.

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.

The data in the call paths view is flat. The presented table is a list, rather than a hierarchy.

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.

Note

Streamline does not walk the stack for kernels, loadable kernel modules, or statically linked drivers. These generate flat data in the call paths view.

Functions that you know are highly used are missing from the reports. Other functions might seem artificially large.

This can be because of code inlining done by the compiler. To turn inlining off, add -fno-inline as an option during compilation.

A newly-generated Capture has no data.

If you experience this and the profiling session had event-based sampling 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.
Was this page helpful? Yes No