From: Jan Kiszka <jan.kiszka@siemens.com>
To: Antonio Quartulli <antonio@mandelbit.com>,
Kieran Bingham <kbingham@kernel.org>
Cc: "open list" <linux-kernel@vger.kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>
Subject: Re: scripts_gdb: Python Exception <class 'gdb.error'>: There is no member named nsections.
Date: Fri, 21 Feb 2025 07:45:07 +0100 [thread overview]
Message-ID: <8e16609a-7e19-4d4a-951f-58c8bd012086@siemens.com> (raw)
In-Reply-To: <85894bbd-05ef-4e40-acf9-98a079c9e2ee@mandelbit.com>
On 20.02.25 16:21, Antonio Quartulli wrote:
> Hi,
>
> I have been working on the new ovpn linux kernel module since a while
> and your gdb kernel debugging helper scripts have been of great help.
>
> However, recently I have started hitting an issue I could not explain.
> When my qemu instance loads the ovpn.ko module, I get the following
> output in gdb:
>
> scanning for modules in /home/ordex/exp/openvpn_dev/linux-ovpn-dco
> loading @0xffffffffa0000000: /home/ordex/exp/openvpn_dev/linux-ovpn-dco/
> drivers/net/ovpn/ovpn.ko
> Python Exception <class 'gdb.error'>: There is no member named nsections.
>
> and the load of the symbols fails.
>
> Does it ring any bell?
> Any help debugging further?
>
> I am running the latest net-next.
>
Thanks for reporting. That's because of [1] in upcoming 6.14. Someone
needs to update scripts/gdb/linux/symbols.py accordingly.
Jan
[1]
https://lore.kernel.org/r/linux-hardening/20241216-sysfs-const-bin_attr-module-v1-1-f81e49e54ce4@weissschuh.net/
--
Siemens AG, Foundational Technologies
Linux Expert Center
next prev parent reply other threads:[~2025-02-21 6:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 15:21 Antonio Quartulli
2025-02-21 6:45 ` Jan Kiszka [this message]
2025-02-21 13:03 ` [PATCH] scripts/gdb/linux/symbols.py: address changes to module_sect_attrs Antonio Quartulli
2025-02-21 16:52 ` Jan Kiszka
2025-02-21 20:33 ` Antonio Quartulli
2025-02-21 20:40 ` [PATCH v2] " Antonio Quartulli
2025-02-26 5:31 ` 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=8e16609a-7e19-4d4a-951f-58c8bd012086@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=antonio@mandelbit.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
/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
all inboxes | Powered by JetHome®