352
edits
Preparing Yocto Development Environment for Debugging: Difference between revisions
Preparing Yocto Development Environment for Debugging (view source)
Revision as of 23:36, 6 February 2019
, 6 February 2019→Perf
(→Strace) |
(→Perf) |
||
| Line 76: | Line 76: | ||
=== Perf === | === Perf === | ||
Tracing and profiling are fundamental on developing, and it is the developer’s responsibility to write code that provides the highest possible performance, so it becomes necessary to analyze programs to find bottlenecks and optimize those regions of code. This analysis can be achieved by using Perf. More specifically, it can be used to solve performance and troubleshooting functions, and answer a variety of questions about code-paths, allocated memory, TCP retransmits, calls to kernel functions, | |||
The following options are the minimum needed for running perf. | |||
'''build/conf/local.conf:''' | '''build/conf/local.conf:''' | ||
| Line 88: | Line 90: | ||
IMAGE_INSTALL += "perf" | IMAGE_INSTALL += "perf" | ||
</syntaxhighlight> | </syntaxhighlight> | ||
=== Valgrind === | === Valgrind === | ||
As you would do for any other package that you want to include in your image and is not part of the default configuration, you need to add the recipe to build it. The source will depend on what board you a using, and you must add the recipe to your meta-layer. Valgrind also needs some of the previously defined features on your '''local.conf''', specifically: | As you would do for any other package that you want to include in your image and is not part of the default configuration, you need to add the recipe to build it. The source will depend on what board you a using, and you must add the recipe to your meta-layer. Valgrind also needs some of the previously defined features on your '''local.conf''', specifically: | ||