From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.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: <bug-31638-13298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31638
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.
https://kojipkgs.fedoraproject.org//packages/kernel/6.8.5/301.fc40/data/logs/x86_64/build.log
+ /usr/bin/find-debuginfo -j48 --strict-build-id -n -i -r -q -p
'.*/usr/bin/perf(.debug)?|.*/usr/libexec/perf-core/.*|.*/usr/lib64/libperf-jvmti.so(.debug)?|XXX'
-o perf-debuginfo.list -p
'.*/usr/lib64/python3.12/site-packages/perf.*so(.debug)?|XXX' -o
python3-perf-debuginfo.list -p '.*/usr/lib64/libperf.so.*(.debug)?|XXX' -o
libperf-debuginfo.list -p
'.*/usr/bin/centrino-decode(.debug)?|.*/usr/bin/powernow-k8-decode(.debug)?|.*/usr/bin/cpupower(.debug)?|.*/usr/lib64/libcpupower.*|.*/usr/bin/turbostat(.debug)?|.*/usr/bin/x86_energy_perf_policy(.debug)?|.*/usr/bin/tmon(.debug)?|.*/usr/bin/lsgpio(.debug)?|.*/usr/bin/gpio-hammer(.debug)?|.*/usr/bin/gpio-event-mon(.debug)?|.*/usr/bin/gpio-watch(.debug)?|.*/usr/bin/iio_event_monitor(.debug)?|.*/usr/bin/iio_generic_buffer(.debug)?|.*/usr/bin/lsiio(.debug)?|.*/usr/bin/intel-speed-select(.debug)?|.*/usr/bin/page_owner_sort(.debug)?|.*/usr/bin/slabinfo(.debug)?|.*/usr/sbin/intel_sdsi(.debug)?|XXX'
-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
'/.*/6.8.5-301.fc40.x86_64[+]debug/.*|/.*6.8.5-301.fc40.x86_64+debug(.debug)?'
-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
`/builddir/build/BUILDROOT/kernel-6.8.5-301.fc40.x86_64/usr/libexec/ksamples/bpf/sock_example':
No debugging symbols
Error while writing index for
`/builddir/build/BUILDROOT/kernel-6.8.5-301.fc40.x86_64/usr/libexec/ksamples/bpf/test-libcap.bin':
No debugging symbols
gdb-add-index: No index was created for
/builddir/build/BUILDROOT/kernel-6.8.5-301.fc40.x86_64/usr/libexec/ksamples/bpf/sock_example
gdb-add-index: [Was there no debuginfo? Was there already an index?]
Error while writing index for
`/builddir/build/BUILDROOT/kernel-6.8.5-301.fc40.x86_64/usr/libexec/ksamples/bpf/test_lru_dist':
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-31638-13298@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=debugedit@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).