From: Jan Kiszka <jan.kiszka@siemens.com>
To: Kieran Bingham <kieran.bingham@linaro.org>,
Peter Griffin <peter.griffin@linaro.org>,
Lee Jones <lee.jones@linaro.org>,
Maxime Coquelin <maxime.coquelin@st.com>,
Russell Wayman <russell.wayman@linaro.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: gdb/scripts: Module symbol search paths
Date: Mon, 14 Mar 2016 11:36:40 +0100 [thread overview]
Message-ID: <56E69438.3030407@siemens.com> (raw)
In-Reply-To: <56E69067.1020909@linaro.org>
Hi Kieran,
On 2016-03-14 11:20, Kieran Bingham wrote:
> Hi Jan,
>
> Whilst testing the modules update patch you sent, I discovered (due to
> having rebased to v4.5) that the module search path will end up picking
> an incorrect version of the .ko file if an earlier version exists.:
>
>
> (gdb) lx-symbols /opt/root/ubuntu-vivid.x86_64
> loading vmlinux
> (gdb) c
> Continuing.
> < load module helloworld.ko on target >
> scanning for modules in /opt/root/ubuntu-vivid.x86_64
> loading @0xffffffffa0000000:
> /opt/root/ubuntu-vivid.x86_64/lib/modules/4.4.0+/extra/helloworld.ko
>
> Looking at the filesystem layout:
>
> kbingham@CookieMonster:~$ sudo find /opt/root/ubuntu-vivid.x86_64/ -name
> helloworld.ko
> /opt/root/ubuntu-vivid.x86_64/lib/modules/4.4.0+/extra/helloworld.ko
> /opt/root/ubuntu-vivid.x86_64/lib/modules/4.5.0+/extra/helloworld.ko
>
If there are multiple sets of modules underneath a path, you have to be
more precise, /opt/root/ubuntu-vivid.x86_64/lib/modules/4.5.0+ in this case.
>
> Unfortunately I can't see any reference to a vfs path in:
> print $lx_module("helloworld")
>
> So we can't retrieve the exact path location from the kernel information
> Have you experienced this issue?
No, because I'm always using lx-symbols against the build output, not
against installed modules. But even then, see above, I don't see a
problem is the path is properly specified.
Jan
>
> Perhaps we ought to prefix our search path with
> $(path_item)/lib/modules/`uname -r`
>
>
> ST's C implementation of module support can be seen at:
>
> https://git.linaro.org/people/kieran.bingham/binutils-gdb.git/blob/e30a18cf086bd02c4ebb57f6f783fe2ad4af9c84:/gdb/stlinux/lkd-modules.c
>
> They restrict the search paths, and parse expected
> lib/modules/{version}/ paths to ensure the correct modules are discovered.
>
> --
> Regards
>
> Kieran
>
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2016-03-14 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 10:20 gdb/scripts: Module symbol search paths Kieran Bingham
2016-03-14 10:36 ` Jan Kiszka [this message]
2016-03-14 10:48 ` Kieran Bingham
2016-03-14 10:55 ` Jan Kiszka
2016-03-14 11:00 ` Kieran Bingham
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=56E69438.3030407@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kieran.bingham@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.coquelin@st.com \
--cc=peter.griffin@linaro.org \
--cc=russell.wayman@linaro.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