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:
Streamline does not show any source code in the Code view.
Make sure that you used the
-goption 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.
-fno-omit-frame-pointeroption 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.
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-inlineas an option during compilation.