352
edits
Preparing Yocto Development Environment for Debugging: Difference between revisions
Preparing Yocto Development Environment for Debugging (view source)
Revision as of 21:13, 11 February 2019
, 11 February 2019→Valgrind
(→Perf) |
|||
| Line 92: | Line 92: | ||
=== Valgrind === | === Valgrind === | ||
Valgrind is a very powerful tool whenever we are dealing with memory leaks and overall trying to find errors of work with memory, but it can also be used for performance profiling, finding synchronization errors in multi-threading programs and analysis of memory consumption. | |||
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: | ||