[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8a20f7ba33426bb6ced600f97f5f67e9d67ea503.camel@linux.ibm.com>
Date: Tue, 05 Aug 2025 15:22:58 +0200
From: Ilya Leoshkevich <iii@...ux.ibm.com>
To: Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann
<daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
Jan Kiszka
<jan.kiszka@...mens.com>,
Kieran Bingham <kbingham@...nel.org>
Cc: linux-kernel@...r.kernel.org, bpf@...r.kernel.org,
Heiko Carstens
<hca@...ux.ibm.com>,
Vasily Gorbik <gor@...ux.ibm.com>,
Alexander Gordeev
<agordeev@...ux.ibm.com>
Subject: Re: [PATCH 0/2] scripts/gdb/symbols: make BPF debug info available
to GDB
On Thu, 2025-07-10 at 13:53 +0200, Ilya Leoshkevich wrote:
> 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
Gentle ping. Any opinions on whether this is valuable? Personally I've
been using this for quite some time, and having source level debugging
for BPF progs (even if variables can't be inspected) feels really nice.
Powered by blists - more mailing lists