From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>
Cc: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH 0/2] scripts/gdb/symbols: make BPF debug info available to GDB
Date: Thu, 10 Jul 2025 13:53:18 +0200 [thread overview]
Message-ID: <20250710115920.47740-1-iii@linux.ibm.com> (raw)
Hi,
This series greatly simplifies debugging BPF progs when using QEMU
gdbstub by providing symbol names, sizes, and line numbers to GDB.
Patch 1 adds radix tree iteration, which is necessary for parsing
prog_idr. Patch 2 is the actual implementation; its description
contains some details on how to use this.
Best regards,
Ilya
Ilya Leoshkevich (2):
scripts/gdb/radix-tree: add lx-radix-tree-command
scripts/gdb/symbols: make BPF debug info available to GDB
scripts/gdb/linux/bpf.py | 253 ++++++++++++++++++++++++++++++
scripts/gdb/linux/constants.py.in | 3 +
scripts/gdb/linux/radixtree.py | 139 +++++++++++++++-
scripts/gdb/linux/symbols.py | 77 ++++++++-
4 files changed, 462 insertions(+), 10 deletions(-)
create mode 100644 scripts/gdb/linux/bpf.py
--
2.50.0
next reply other threads:[~2025-07-10 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 11:53 Ilya Leoshkevich [this message]
2025-07-10 11:53 ` [PATCH 1/2] scripts/gdb/radix-tree: add lx-radix-tree-command Ilya Leoshkevich
2025-07-10 11:53 ` [PATCH 2/2] scripts/gdb/symbols: make BPF debug info available to GDB Ilya Leoshkevich
2025-08-05 13:22 ` [PATCH 0/2] " Ilya Leoshkevich
2025-08-05 16:48 ` Alexei Starovoitov
2025-08-27 11:26 ` Ilya Leoshkevich
2025-10-30 16:47 ` Jan Kiszka
2025-11-05 19:32 ` Ilya Leoshkevich
2025-11-06 6:07 ` Jan Kiszka
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=20250710115920.47740-1-iii@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).