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] scripts/gdb: use mem instead of core_layout to get the module address
Date: Wed, 12 Apr 2023 10:06:59 -0700 [thread overview]
Message-ID: <ZDblM40+MVm9XTgT@bombadil.infradead.org> (raw)
In-Reply-To: <20230412111508.892296-1-p.raghav@samsung.com>
On Wed, Apr 12, 2023 at 01:15:08PM +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>
> ---
Jan, Kieran,
That commit is in my modules-next tree, so I can take that fix in
through my tree. Let me know if that is OK, and if you ACK the patch.
Pankaj, thanks!
Luis
prev parent reply other threads:[~2023-04-12 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230412112345eucas1p10c0ab064156268c9021abe9fc6bf1fd3@eucas1p1.samsung.com>
2023-04-12 11:15 ` Pankaj Raghav
[not found] ` <CGME20230412112608eucas1p2e8aa819cf92ccc2bacfe0ff9bfcd7a6f@eucas1p2.samsung.com>
2023-04-12 11:26 ` Pankaj Raghav
2023-04-12 17:52 ` Florian Fainelli
2023-04-12 20:06 ` Pankaj Raghav
2023-04-12 17:06 ` Luis Chamberlain [this message]
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=ZDblM40+MVm9XTgT@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®