GitHub pull request #3393 of commit ac00834ed3fdb7fd536a97364cda9c141a75edd4, no merge conflicts.sha1origin/pr/3393/mergeghprbActualCommitac00834ed3fdb7fd536a97364cda9c141a75edd4ghprbActualCommitAuthorghprbActualCommitAuthorEmailghprbAuthorRepoGitUrlhttps://github.com/rupran/bcc.gitghprbTriggerAuthorghprbTriggerAuthorEmailghprbTriggerAuthorLoginyonghong-songghprbTriggerAuthorLoginMention@yonghong-songghprbPullId3393ghprbTargetBranchmasterghprbSourceBranchlibdebuginfodGIT_BRANCHlibdebuginfodghprbPullAuthorEmailziegler@einserver.deghprbPullAuthorLoginrupranghprbPullAuthorLoginMention@rupranghprbPullDescriptionGitHub pull request #3393 of commit ac00834ed3fdb7fd536a97364cda9c141a75edd4, no merge conflicts.ghprbPullTitlebcc_elf: add support for debug information from libdebuginfodghprbPullLinkhttps://github.com/iovisor/bcc/pull/3393ghprbPullLongDescriptionThis change adds debuginfod as a new source for debug information. By using libdebuginfod we can query a server for a file containing debug information for a given ELF binary. The environment variable `DEBUGINFOD_URLS` has to be defined to an URL for a debuginfod server providing debug information files for your distribution or the federating server provided by the elfutils project:\r\n\r\nFor example, to use the Fedora server, you would need:\r\n```sh\r\n$ export DEBUGINFOD_URLS=\"https://debuginfod.fedoraproject.org/\"\r\n```\r\n\r\nOr for the elfutils server which federates to servers for openSUSE, Void Linux, Debian and Fedora, among others: \r\n```sh\r\n$ export DEBUGINFOD_URLS=\"https://debuginfod.elfutils.org/\"\r\n```\r\n\r\nCalls to the `debuginfod_find_debuginfo` function from libdebuginfod will fail if the environment variable is not set, otherwise the library will attempt to download debug information for a build ID extracted from the binary in question and store it in a local cache directory.\r\n\r\nFixes iovisor/bpftrace#1774\r\n\r\nWhile this first implementation works fine with and without libdebuginfod installed, I'm not sure about the way it should be integrated into the build system. For now, a check for the library is performed in `cmake/FindLibElf.cmake` and if it was found, the `HAVE_LIBDEBUGINFOD` definition is added to the compile options for `libbcc`. In addition, I'm not sure if we should already put the dependency on libdebuginfod1 and libdebuginfod-dev into `debian/control`, as it is only available from `buster-backports` on Debian Buster. I'd be happy if someone with more experience could give me advice on these decisions.ghprbCommentBody[buildbot, test this please]ghprbGhRepositoryiovisor/bccghprbCredentialsId6d3daf13-69b8-48b1-9c8f-ec5353264113false<a title="bcc_elf: add support for debug information from libdebuginfod" href="https://github.com/iovisor/bcc/pull/3393">PR #3393</a>: bcc_elf: add support for de...#97211869127460664bcc-pr #972972false9727785SUCCESS1620540580684https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/972/git972https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/label=fc25/972/972https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/label=fc26/972/972https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/label=fc27/972/972https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/label=fc28/972/972https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/label=ubuntu1604/972/972https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/label=ubuntu1710/972/972https://buildbot.iovisor.org/jenkins/user/danobi/my-views/view/all/job/bcc-pr/label=ubuntu1804/972/