public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "james.hilliard1 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106773] libbpf: failed to find BTF info for global/extern symbol 'bpf_link_fops' Date: Thu, 01 Dec 2022 22:11:05 +0000 [thread overview] Message-ID: <bug-106773-4-ZOVLtunXh3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106773-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106773 --- Comment #11 from James Hilliard <james.hilliard1 at gmail dot com> --- Also hitting this one in cgroup_hierarchical_stats.c: $ /home/buildroot/bpf-next/tools/testing/selftests/bpf/tools/sbin/bpftool --debug gen skeleton /home/buildroot/bpf-next/tools/testing/selftests/bpf/bpf_gcc/cgroup_hierarchical_stats.bpf.linked3.o name cgroup_hierarchical_stat libbpf: loading object 'cgroup_hierarchical_stat' from buffer libbpf: elf: section(2) .symtab, size 504, link 1, flags 0, type=2 libbpf: elf: section(3) .data, size 0, link 0, flags 3, type=1 libbpf: elf: skipping section(3) .data (size 0) libbpf: elf: section(4) .bss, size 0, link 0, flags 3, type=8 libbpf: elf: section(5) fentry/cgroup_attach_task, size 264, link 0, flags 6, type=1 libbpf: sec 'fentry/cgroup_attach_task': found program 'counter' at insn offset 0 (0 bytes), code size 33 insns (264 bytes) libbpf: elf: section(6) fentry/bpf_rstat_flush, size 656, link 0, flags 6, type=1 libbpf: sec 'fentry/bpf_rstat_flush': found program 'flusher' at insn offset 0 (0 bytes), code size 82 insns (656 bytes) libbpf: elf: section(7) iter.s/cgroup, size 352, link 0, flags 6, type=1 libbpf: sec 'iter.s/cgroup': found program 'dumper' at insn offset 0 (0 bytes), code size 44 insns (352 bytes) libbpf: elf: section(8) .rodata, size 67, link 0, flags 2, type=1 libbpf: elf: section(9) .maps, size 64, link 0, flags 3, type=1 libbpf: elf: section(10) license, size 4, link 0, flags 3, type=1 libbpf: license of cgroup_hierarchical_stat is GPL libbpf: elf: section(11) .comment, size 43, link 0, flags 30, type=1 libbpf: elf: skipping unrecognized data section(11) .comment libbpf: elf: section(12) .relfentry/cgroup_attach_task, size 48, link 2, flags 40, type=9 libbpf: elf: section(13) .relfentry/bpf_rstat_flush, size 96, link 2, flags 40, type=9 libbpf: elf: section(14) .reliter.s/cgroup, size 64, link 2, flags 40, type=9 libbpf: elf: section(15) .BTF, size 468873, link 0, flags 0, type=1 libbpf: looking for externs among 21 symbols... libbpf: failed to find BTF for extern 'cgroup_rstat_updated' [8134] section: -2 Error: failed to open BPF object file: No such file or directory
next prev parent reply other threads:[~2022-12-01 22:11 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-29 22:07 [Bug c/106773] New: " james.hilliard1 at gmail dot com 2022-09-01 20:31 ` [Bug target/106773] " james.hilliard1 at gmail dot com 2022-09-01 22:33 ` james.hilliard1 at gmail dot com 2022-11-29 0:44 ` david.faust at oracle dot com 2022-11-30 21:20 ` david.faust at oracle dot com 2022-12-01 0:04 ` james.hilliard1 at gmail dot com 2022-12-01 0:12 ` james.hilliard1 at gmail dot com 2022-12-01 2:07 ` james.hilliard1 at gmail dot com 2022-12-01 17:09 ` david.faust at oracle dot com 2022-12-01 21:49 ` david.faust at oracle dot com 2022-12-01 22:09 ` james.hilliard1 at gmail dot com 2022-12-01 22:11 ` james.hilliard1 at gmail dot com [this message] 2022-12-01 22:30 ` james.hilliard1 at gmail dot com 2022-12-05 17:42 ` david.faust at oracle dot com 2022-12-05 19:01 ` james.hilliard1 at gmail dot com 2022-12-05 21:06 ` david.faust at oracle dot com 2022-12-05 21:57 ` james.hilliard1 at gmail dot com 2022-12-14 18:25 ` cvs-commit at gcc dot gnu.org 2022-12-14 18:25 ` cvs-commit at gcc dot gnu.org 2022-12-14 18:26 ` cvs-commit at gcc dot gnu.org 2023-01-06 14:18 ` jemarch at gcc dot gnu.org
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-106773-4-ZOVLtunXh3@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).