Bug 13807 - add support for elfutils debuginfod #yocto


Dorinda
 

Hello Everyone,
I am an Outreachy internship applicant, and I would love to assist on this bug #13807 - add support for elfutils debug info server.
I would like some more detailed information about this bug, and what's needed to get started on this task.
Thanks.


Ross Burton <ross@...>
 

Hi Dorina,

On Sat, 10 Oct 2020 at 02:30, Dorinda <dorindabassey@...> wrote:
I am an Outreachy internship applicant, and I would love to assist on this bug #13807 - add support for elfutils debug info server.
I would like some more detailed information about this bug, and what's needed to get started on this task.
The first comment on the bug gives a brief overview:

1) Enable debuginfod in elfutils. This should be a PACKAGECONFIG, and
the build needs some extra dependencies (libmicrohttpd curl sqlite3
libarchive). Initially disabled by default. This should be
relatively straightforward once you understand how a recipe is written
and how PACKAGECONFIG works. All of those extra dependencies are in
oe-core already apart from libmicrohttpd which is part of meta-oe, so
you'll need to add that layer to your build configuration.

2) Add support for ipkg to the debuginfod scanner. 0.178 only supports
RPM but the next release (and git master) can also scan .debs, and as
ipkgs are binary-compatible with dpkg then this is a trivial addition
to the filename matching. This is literally a two line patch to
elfutils.

3) Verify that running debuginfod manually over $DEPLOY_DIR and
setting DEBUGINFOD_URLS correctly works. Test case: debuginfod-find
source hexcode /bin/bash.

4) Determine final integration. Straw man proposal: a class that turns
on debuginfod for elfutils and sets DEBUGINFOD_URLS in the image, and
a script that runs the elfutils-native debuginfod on DEPLOY_DIR.

The first step is critical so start with the Yocto Project
documentation and understand how a recipe is written.

Regards,
Ross