public inbox for
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <>
Subject: [Bug find-debuginfo/31638] New: Recognize (and skip) bpf (kernel) files
Date: Sat, 13 Apr 2024 10:23:43 +0000	[thread overview]
Message-ID: <> (raw)

            Bug ID: 31638
           Summary: Recognize (and skip) bpf (kernel) files
           Product: debugedit
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: find-debuginfo
          Assignee: unassigned at sourceware dot org
          Reporter: mark at klomp dot org
                CC: debugedit at sourceware dot org
  Target Milestone: ---

find-debuginfo thinks the BPF files are "normal" ELF files and calls
gdb-add-index on them. But the BPF files aren't "normal" and don't have any
debuginfo. So gdb-add-index fails.

See e.g.

+ /usr/bin/find-debuginfo -j48 --strict-build-id -n -i -r -q -p
-o perf-debuginfo.list -p
'.*/usr/lib64/python3.12/site-packages/perf.*so(.debug)?|XXX' -o
python3-perf-debuginfo.list -p '.*/usr/lib64/*(.debug)?|XXX' -o
libperf-debuginfo.list -p
-o kernel-tools-debuginfo.list -p '.*/usr/sbin/bpftool(.debug)?|XXX' -o
bpftool-debuginfo.list -p '.*/usr/libexec/(ksamples|kselftests)/.*|XXX' -o
selftests-debuginfo.list --keep-section .BTF -p '.*/usr/src/kernels/.*|XXX' -o
ignored-debuginfo.list -p
-o debuginfodebug.list --keep-section .BTF -p '.*/usr/src/kernels/.*|XXX' -o
ignored-debuginfo.list -p
'/.*/6.8.5-301.fc40.x86_64/.*|/.*6.8.5-301.fc40.x86_64(.debug)?' -o
debuginfo.list /builddir/build/BUILD/kernel-6.8.5
Error while writing index for
No debugging symbols
Error while writing index for
No debugging symbols
gdb-add-index: No index was created for
gdb-add-index: [Was there no debuginfo? Was there already an index?]
Error while writing index for
No debugging symbols

You are receiving this mail because:
You are on the CC list for the bug.

                 reply	other threads:[~2024-04-13 10:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).