diff options
Diffstat (limited to 'documentation/dev-manual/debugging.rst')
-rw-r--r-- | documentation/dev-manual/debugging.rst | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/documentation/dev-manual/debugging.rst b/documentation/dev-manual/debugging.rst index f433e8e6a9..921022475f 100644 --- a/documentation/dev-manual/debugging.rst +++ b/documentation/dev-manual/debugging.rst | |||
@@ -297,11 +297,11 @@ If you are unsure whether a variable dependency is being picked up | |||
297 | automatically for a given task, you can list the variable dependencies | 297 | automatically for a given task, you can list the variable dependencies |
298 | BitBake has determined by doing the following: | 298 | BitBake has determined by doing the following: |
299 | 299 | ||
300 | 1. Build the recipe containing the task:: | 300 | #. Build the recipe containing the task:: |
301 | 301 | ||
302 | $ bitbake recipename | 302 | $ bitbake recipename |
303 | 303 | ||
304 | 2. Inside the :term:`STAMPS_DIR` | 304 | #. Inside the :term:`STAMPS_DIR` |
305 | directory, find the signature data (``sigdata``) file that | 305 | directory, find the signature data (``sigdata``) file that |
306 | corresponds to the task. The ``sigdata`` files contain a pickled | 306 | corresponds to the task. The ``sigdata`` files contain a pickled |
307 | Python database of all the metadata that went into creating the input | 307 | Python database of all the metadata that went into creating the input |
@@ -319,7 +319,7 @@ BitBake has determined by doing the following: | |||
319 | the cached task output. The ``siginfo`` files contain exactly the | 319 | the cached task output. The ``siginfo`` files contain exactly the |
320 | same information as ``sigdata`` files. | 320 | same information as ``sigdata`` files. |
321 | 321 | ||
322 | 3. Run ``bitbake-dumpsig`` on the ``sigdata`` or ``siginfo`` file. Here | 322 | #. Run ``bitbake-dumpsig`` on the ``sigdata`` or ``siginfo`` file. Here |
323 | is an example:: | 323 | is an example:: |
324 | 324 | ||
325 | $ bitbake-dumpsig ${BUILDDIR}/tmp/stamps/i586-poky-linux/db/6.0.30-r1.do_fetch.sigdata.7c048c18222b16ff0bcee2000ef648b1 | 325 | $ bitbake-dumpsig ${BUILDDIR}/tmp/stamps/i586-poky-linux/db/6.0.30-r1.do_fetch.sigdata.7c048c18222b16ff0bcee2000ef648b1 |
@@ -992,7 +992,7 @@ site <https://sourceware.org/gdb/documentation/>`__. | |||
992 | The following steps show you how to debug using the GNU project | 992 | The following steps show you how to debug using the GNU project |
993 | debugger. | 993 | debugger. |
994 | 994 | ||
995 | 1. *Configure your build system to construct the companion debug | 995 | #. *Configure your build system to construct the companion debug |
996 | filesystem:* | 996 | filesystem:* |
997 | 997 | ||
998 | In your ``local.conf`` file, set the following:: | 998 | In your ``local.conf`` file, set the following:: |
@@ -1012,7 +1012,7 @@ debugger. | |||
1012 | the full filesystem for debugging. Subsequent steps in this procedure | 1012 | the full filesystem for debugging. Subsequent steps in this procedure |
1013 | show how to combine the partial filesystem with the full filesystem. | 1013 | show how to combine the partial filesystem with the full filesystem. |
1014 | 1014 | ||
1015 | 2. *Configure the system to include gdbserver in the target filesystem:* | 1015 | #. *Configure the system to include gdbserver in the target filesystem:* |
1016 | 1016 | ||
1017 | Make the following addition in your ``local.conf`` file:: | 1017 | Make the following addition in your ``local.conf`` file:: |
1018 | 1018 | ||
@@ -1021,7 +1021,7 @@ debugger. | |||
1021 | The change makes | 1021 | The change makes |
1022 | sure the ``gdbserver`` package is included. | 1022 | sure the ``gdbserver`` package is included. |
1023 | 1023 | ||
1024 | 3. *Build the environment:* | 1024 | #. *Build the environment:* |
1025 | 1025 | ||
1026 | Use the following command to construct the image and the companion | 1026 | Use the following command to construct the image and the companion |
1027 | Debug Filesystem:: | 1027 | Debug Filesystem:: |
@@ -1057,7 +1057,7 @@ debugger. | |||
1057 | the actual image (e.g. ``gdb-cross-i586``). The suggestion is usually the | 1057 | the actual image (e.g. ``gdb-cross-i586``). The suggestion is usually the |
1058 | actual name you want to use. | 1058 | actual name you want to use. |
1059 | 1059 | ||
1060 | 4. *Set up the* ``debugfs``\ *:* | 1060 | #. *Set up the* ``debugfs``\ *:* |
1061 | 1061 | ||
1062 | Run the following commands to set up the ``debugfs``:: | 1062 | Run the following commands to set up the ``debugfs``:: |
1063 | 1063 | ||
@@ -1066,7 +1066,7 @@ debugger. | |||
1066 | $ tar xvfj build-dir/tmp/deploy/images/machine/image.rootfs.tar.bz2 | 1066 | $ tar xvfj build-dir/tmp/deploy/images/machine/image.rootfs.tar.bz2 |
1067 | $ tar xvfj build-dir/tmp/deploy/images/machine/image-dbg.rootfs.tar.bz2 | 1067 | $ tar xvfj build-dir/tmp/deploy/images/machine/image-dbg.rootfs.tar.bz2 |
1068 | 1068 | ||
1069 | 5. *Set up GDB:* | 1069 | #. *Set up GDB:* |
1070 | 1070 | ||
1071 | Install the SDK (if you built one) and then source the correct | 1071 | Install the SDK (if you built one) and then source the correct |
1072 | environment file. Sourcing the environment file puts the SDK in your | 1072 | environment file. Sourcing the environment file puts the SDK in your |
@@ -1075,7 +1075,7 @@ debugger. | |||
1075 | If you are using the build system, Gdb is located in | 1075 | If you are using the build system, Gdb is located in |
1076 | `build-dir`\ ``/tmp/sysroots/``\ `host`\ ``/usr/bin/``\ `architecture`\ ``/``\ `architecture`\ ``-gdb`` | 1076 | `build-dir`\ ``/tmp/sysroots/``\ `host`\ ``/usr/bin/``\ `architecture`\ ``/``\ `architecture`\ ``-gdb`` |
1077 | 1077 | ||
1078 | 6. *Boot the target:* | 1078 | #. *Boot the target:* |
1079 | 1079 | ||
1080 | For information on how to run QEMU, see the `QEMU | 1080 | For information on how to run QEMU, see the `QEMU |
1081 | Documentation <https://wiki.qemu.org/Documentation/GettingStartedDevelopers>`__. | 1081 | Documentation <https://wiki.qemu.org/Documentation/GettingStartedDevelopers>`__. |
@@ -1084,7 +1084,7 @@ debugger. | |||
1084 | 1084 | ||
1085 | Be sure to verify that your host can access the target via TCP. | 1085 | Be sure to verify that your host can access the target via TCP. |
1086 | 1086 | ||
1087 | 7. *Debug a program:* | 1087 | #. *Debug a program:* |
1088 | 1088 | ||
1089 | Debugging a program involves running gdbserver on the target and then | 1089 | Debugging a program involves running gdbserver on the target and then |
1090 | running Gdb on the host. The example in this step debugs ``gzip``: | 1090 | running Gdb on the host. The example in this step debugs ``gzip``: |
@@ -1116,7 +1116,7 @@ debugger. | |||
1116 | users ``~/.gdbinit`` file. Upon starting, Gdb automatically runs whatever | 1116 | users ``~/.gdbinit`` file. Upon starting, Gdb automatically runs whatever |
1117 | commands are in that file. | 1117 | commands are in that file. |
1118 | 1118 | ||
1119 | 8. *Deploying without a full image rebuild:* | 1119 | #. *Deploying without a full image rebuild:* |
1120 | 1120 | ||
1121 | In many cases, during development you want a quick method to deploy a | 1121 | In many cases, during development you want a quick method to deploy a |
1122 | new binary to the target and debug it, without waiting for a full | 1122 | new binary to the target and debug it, without waiting for a full |