dev-manual/common-tasks.rst: correct the documentation for debuginfod
PATCH 1/1 dev-manual/common-tasks.rst: correct the documentation for debuginfod
Particularly,
- correctly describe the use of DEBUGINFOD_URLS; drop it from bitbake variables
- all necessary component tweaks are enabled by default via DISTRO_FEATURES
- provide on-target examples of what to look for when things work properly
--- documentation/dev-manual/common-tasks.rst | 40 ++++++++++++++--------- documentation/ref-manual/variables.rst | 6 ---- 2 files changed, 24 insertions(+), 22 deletions(-)
documentation/dev-manual/common-tasks.rst +24 -16
@@ -9705,39 +9705,47 @@ methods you can use: running a debuginfod server and using gdbserver. Using the debuginfod server method ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -"debuginfod" from "elfutils" is a way to distribute "debuginfo" files. -Running a "debuginfod" server makes debug symbols readily available, +``debuginfod`` from ``elfutils`` is a way to distribute ``debuginfo`` files. +Running a ``debuginfod`` server makes debug symbols readily available, which means you don't need to download debugging information and the binaries of the process being debugged. You can just fetch debug symbols from the server. -To run a debuginfod server, you need to do the following: +To run a ``debuginfod`` server, you need to do the following: -- Ensure that this variable is set in your ``local.conf`` file:: +- Ensure that ``debuginfod`` is present in :term:`DISTRO_FEATURES` + (it already is in ``OpenEmbedded-core`` defaults and ``poky`` reference distribution). + If not, set in your distro config file or in ``local.conf``:: - PACKAGECONFIG_pn-elfutils-native = "debuginfod libdebuginfod" + DISTRO_FEATURES_append = " debuginfod" - This :term:`PACKAGECONFIG` option enables debuginfod and libdebuginfod for - "elfutils-native". + This distro feature enables the server and client library in ``elfutils``, + and enables ``debuginfod`` support in clients (at the moment, ``gdb`` and ``binutils``). -- Run the following commands to set up the "debuginfod" server:: +- Run the following commands to launch the ``debuginfod`` server on the host:: $ oe-debuginfod +- To use ``debuginfod`` on the target, you need to know the ip:port where + ``debuginfod`` is listening on the host (port defaults to 8002), and export + that into the shell environment, for example in ``qemu``:: -To use debuginfod on the target, you need the following: + root@qemux86-64:~# export DEBUGINFOD_URLS="http://192.168.7.1:8002/" -- Ensure that this variable is set in your ``local.conf`` file:: +- Then debug info fetching should simply work when running the target ``gdb``, + ``readelf`` or ``objdump``, for example:: - DEBUGINFOD_URLS = "http://localhost:8002/" + root@qemux86-64:~# gdb /bin/cat + ... + Reading symbols from /bin/cat... + Downloading separate debug info for /bin/cat... + Reading symbols from /home/root/.cache/debuginfod_client/923dc4780cfbc545850c616bffa884b6b5eaf322/debuginfo... - This :term:`DEBUGINFOD_URLS` option does the client configuration. +- It's also possible to use ``debuginfod-find`` to just query the server:: - :: - - PACKAGECONFIG_pn-gdb = "debuginfod" + root@qemux86-64:~# debuginfod-find debuginfo /bin/ls + /home/root/.cache/debuginfod_client/356edc585f7f82d46f94fcb87a86a3fe2d2e60bd/debuginfo - This :term:`PACKAGECONFIG` option enables "debuginfod" for "gdb". Using the gdbserver method ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
documentation/ref-manual/variables.rst +0 -6
@@ -1523,12 +1523,6 @@ system and gives an overview of their function and contents. DEBIANNAME_${PN} = "dbus-1" - :term:`DEBUGINFOD_URLS` - Points to the URL of the "debuginfod" server. Such that for every - debugging information lookup, the debuginfod client will query the - server and return the requested information. You set this variable - in your ``local.conf`` file. - :term:`DEBUG_BUILD` Specifies to build packages with debugging information. This influences the value of the ``SELECTED_OPTIMIZATION`` variable.
Signature · 1 line
2.30.2
Hi Alex,
Could you please add the v2/v3/vwhatever in the mail subject next time? You can do so by passing -v 2 to git format-patch. This helps us keep track of which version of a patch should be merged (well, it helps Michael :p) and on which patch series to answer/rewview.
No need to do it this time :)
Thanks for the patch, LGTM!
Quentin
Michael Opdenacker
Reviewed-byHi Alex,
Quoted 8 lines · Quentin Schulz
Hi Alex,
Could you please add the v2/v3/vwhatever in the mail subject next time? You can do so by passing
-v 2togit format-patch. This helps us keep track of which version of a patch should be merged (well, it helps Michael :p) and on which patch series to answer/rewview.No need to do it this time :)
I agree :)
Thanks for the patch.
Merged into the "master-next" branch of the yocto-docs repository
(http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/log/?h=master-next).
I should send a new pull-request for inclusion in "master" by the end of the week.
Thanks again,
Michael.
Signature · 3 lines
Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Thanks, I'll remember to send versioned patches!
Alex
Quoted 34 lines · Michael Opdenacker
Hi Alex,
Quoted 8 lines · Quentin Schulz
Hi Alex,
Could you please add the v2/v3/vwhatever in the mail subject next time? You can do so by passing
-v 2togit format-patch. This helps us keep track of which version of a patch should be merged (well, it helps Michael :p) and on which patch series to answer/rewview.No need to do it this time :)
I agree :)
Thanks for the patch.
Reviewed-by Michael Opdenacker <[email protected]>Merged into the "master-next" branch of the yocto-docs repository
(http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/log/?h=master-next).
I should send a new pull-request for inclusion in "master" by the end of the week.Thanks again,
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com