From: Tw <tw19881113@gmail.com>
To: bpf@vger.kernel.org
Cc: Tw <tw19881113@gmail.com>
Subject: [PATCH v2] libbpf: Ignore exception frame section
Date: Mon, 24 Aug 2026 21:01:33 +0800 [thread overview]
Message-ID: <20260824130245.580545-1-tw19881113@gmail.com> (raw)
Exception handling in BPF program is not supported right now, let's skip it.
BTW, I found this when building BPF with Zig compiler[1].
[1]: https://github.com/tw4452852/bb
Signed-off-by: Tw <tw19881113@gmail.com>
---
v2:
Revise the commit message.
tools/lib/bpf/libbpf.c | 3 ++-
tools/lib/bpf/linker.c | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
index b749c0174..05727c418 100644
--- a/tools/lib/bpf/libbpf.c
+++ b/tools/lib/bpf/libbpf.c
@@ -3867,7 +3867,8 @@ static Elf64_Rel *elf_rel_by_idx(Elf_Data *data, size_t idx)
static bool is_sec_name_dwarf(const char *name)
{
/* approximation, but the actual list is too long */
- return str_has_pfx(name, ".debug_");
+ return str_has_pfx(name, ".debug_") ||
+ strcmp(name, ".eh_frame") == 0;
}
static bool ignore_elf_section(Elf64_Shdr *hdr, const char *name)
diff --git a/tools/lib/bpf/linker.c b/tools/lib/bpf/linker.c
index 78f92c392..1fb0efdbf 100644
--- a/tools/lib/bpf/linker.c
+++ b/tools/lib/bpf/linker.c
@@ -599,7 +599,8 @@ int bpf_linker__add_buf(struct bpf_linker *linker, void *buf, size_t buf_sz,
static bool is_dwarf_sec_name(const char *name)
{
/* approximation, but the actual list is too long */
- return strncmp(name, ".debug_", sizeof(".debug_") - 1) == 0;
+ return strncmp(name, ".debug_", sizeof(".debug_") - 1) == 0 ||
+ strcmp(name, ".eh_frame") == 0;
}
static bool is_ignored_sec(struct src_sec *sec)
--
2.54.0
next reply other threads:[~2026-08-24 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 13:01 Tw [this message]
2026-08-24 13:08 ` [PATCH v2] libbpf: Ignore exception frame section Kumar Kartikeya Dwivedi
2026-08-24 13:44 ` bot+bpf-ci
2026-08-24 19:55 ` Andrii Nakryiko
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=20260824130245.580545-1-tw19881113@gmail.com \
--to=tw19881113@gmail.com \
--cc=bpf@vger.kernel.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