documentation/dev-manual/debugging.rst

3 Debugging Tools and Techniques
6 The exact method for debugging build failures depends on the nature of
8 Standard debugging practices such as comparison against the last known
13 provides some general tips to aid in debugging given a variety of
18    A useful feature for debugging is the error reporting tool.
28 The following list shows the debugging topics in the remainder of this
31 -  ":ref:`dev-manual/debugging:viewing logs from failed tasks`" describes
35 -  ":ref:`dev-manual/debugging:viewing variable values`" describes how to
39 -  ":ref:`dev-manual/debugging:viewing package information with \`\`oe-pkgdata-util\`\``"
44 -  ":ref:`dev-manual/debugging:viewing dependencies between recipes and tasks`"
48 -  ":ref:`dev-manual/debugging:viewing task variable dependencies`" describes
53 -  ":ref:`dev-manual/debugging:running specific tasks`" describes
58 -  ":ref:`dev-manual/debugging:general BitBake problems`" describes how
62 -  ":ref:`dev-manual/debugging:building with no dependencies`"
66 -  ":ref:`dev-manual/debugging:recipe logging mechanisms`"
68    debugging output and report errors and warnings.
70 -  ":ref:`dev-manual/debugging:debugging parallel make races`"
76 -  ":ref:`dev-manual/debugging:debugging with the gnu project debugger (gdb) remotely`"
80 -  ":ref:`dev-manual/debugging:debugging with the gnu project debugger (gdb) on the target`"
81    describes how to use GDB directly on target hardware for debugging.
83 -  ":ref:`dev-manual/debugging:other debugging tips`" describes
84    miscellaneous debugging tips that can be useful.
142 helpful during debugging.
346 Debugging signature construction and unexpected task executions
381 state (sstate) task can be a useful debugging aid. This information is
386 ":ref:`dev-manual/debugging:viewing task variable dependencies`" section.
574 debugging output and reporting errors and warnings. For Python
672 Debugging Parallel Make Races
895 Debugging With the GNU Project Debugger (GDB) Remotely
914 constraints arise because GDB needs to load the debugging information
918 before starting the debugging process. These extra computations place
930 which means you don't need to download debugging information
974 debugging information from the debugged process. Instead, a GDB instance
975 processes the debugging information that is run on a remote computer -
978 memory regions of that debugged program. All the debugging information
979 loaded and processed as well as all the heavy debugging is done by the
983 Because the host GDB is responsible for loading the debugging
985 debugging happen, you have to make sure the host can access the
986 unstripped binaries complete with their debugging information and also
989 program. Because gdbserver does not need any local debugging
1019    the full filesystem for debugging. Subsequent steps in this procedure
1039    make it available for debugging. Build the SDK that matches the
1041    used later for debugging, especially during long term maintenance::
1057    ``cross-gdb`` you can use for debugging during development. While
1096    Debugging a program involves running gdbserver on the target and then
1147 Debugging with the GNU Project Debugger (GDB) on the Target
1150 The previous section addressed using GDB remotely for debugging
1152 limitations on many embedded devices. However, debugging in the target
1157 To support this kind of debugging, you need do the following:
1185    recommended only for debugging purposes.
1202 Other Debugging Tips