If the data in your reports seems incomplete, it could indicate that you did not include a compilation option essential to Streamline. Consult the following common report problems and solutions.
- Symptom
Streamline does not show any source code in the Code view.
- Solution
Make sure that you used the
-goption 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 run configuration dialog. Press the Add Library... button 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
-f-no-omit-frame-pointeroption during compilation and be sure to check the Call Stack Unwinding option in the run configuration dialog.Note
Streamline does not walk the stack for kernels or statically linked drivers. Both 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 due to code inlining done by the compiler. Turn inlining off by adding
-fno-inlineas an option during compilation.
See also- Reference
PDF version