From: Luis Chamberlain <mcgrof@kernel.org>
To: Pankaj Raghav <p.raghav@samsung.com>
Cc: jan.kiszka@siemens.com, kbingham@kernel.org,
gost.dev@samsung.com, linux-kernel@vger.kernel.org,
song@kernel.org
Subject: Re: [PATCH v2] scripts/gdb: use mem instead of core_layout to get the module address
Date: Wed, 12 Apr 2023 17:53:11 -0700 [thread overview]
Message-ID: <ZDdSd8iB2n6r/ccB@bombadil.infradead.org> (raw)
In-Reply-To: <20230412202516.1027149-1-p.raghav@samsung.com>
On Wed, Apr 12, 2023 at 10:25:18PM +0200, Pankaj Raghav wrote:
> commit ac3b43283923 ("module: replace module_layout with module_memory")
> changed the struct module data structure from module_layout to
> module_memory. The core_layout member which is used while loading
> modules are not available anymore leading to the following error while
> running gdb:
>
> (gdb) lx-symbols
> loading vmlinux
> Python Exception <class 'gdb.error'>: There is no member named core_layout.
> Error occurred in Python: There is no member named core_layout.
>
> Replace core_layout with its new counterpart mem[MOD_TEXT].
>
> Fixes: ac3b43283923 ("module: replace module_layout with module_memory")
> Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>
> ---
> scripts/gdb/linux/constants.py.in | 3 +++
> scripts/gdb/linux/modules.py | 4 ++--
> scripts/gdb/linux/symbols.py | 4 ++--
> 3 files changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/scripts/gdb/linux/constants.py.in b/scripts/gdb/linux/constants.py.in
> index 36fd2b145853..471300ba176c 100644
> --- a/scripts/gdb/linux/constants.py.in
> +++ b/scripts/gdb/linux/constants.py.in
> @@ -62,6 +62,9 @@ LX_GDBPARSED(hrtimer_resolution)
> LX_GDBPARSED(IRQD_LEVEL)
> LX_GDBPARSED(IRQ_HIDDEN)
>
> +/* linux/module.h */
> +LX_GDBPARSED(MOD_TEXT)
Should we just fill in the rest of the other sections too while at it?
Luis
next prev parent reply other threads:[~2023-04-13 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230412203420eucas1p2efd38df12efde2ca05c6b3a26f5a753b@eucas1p2.samsung.com>
2023-04-12 20:25 ` Pankaj Raghav
2023-04-13 0:53 ` Luis Chamberlain [this message]
2023-04-13 7:44 ` Pankaj Raghav
2023-04-13 13:47 ` Kieran Bingham
2023-04-13 21:04 ` Luis Chamberlain
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=ZDdSd8iB2n6r/ccB@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=gost.dev@samsung.com \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.raghav@samsung.com \
--cc=song@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
all inboxes | Powered by JetHome®