From: Jan Kiszka <jan.kiszka@siemens.com>
To: Stefano Garzarella <sgarzare@redhat.com>,
Kieran Bingham <kbingham@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: scripts/gdb: received an error when invoking lx-symbols
Date: Wed, 22 Jul 2020 11:19:42 +0200 [thread overview]
Message-ID: <04728663-acde-bfb7-84dc-f97d628bc739@siemens.com> (raw)
In-Reply-To: <20200722091342.c3iss32caiuuizja@steredhat>
On 22.07.20 11:13, Stefano Garzarella wrote:
> Hi Jan, Kieran,
> with the last Linux 5.8-rc6 I have some problems with gdb scripts.
> Everything is fine with Linux 5.7.
>
> When I call lx-symbols, I received this error while loading modules
> symbols:
>
> (gdb) set python print-stack full
> (gdb) target remote :1234
> Remote debugging using :1234
> arch_atomic_read (v=<optimized out>) at ../arch/x86/kernel/process.c:687
> 687 trace_cpu_idle_rcuidle(PWR_EVENT_EXIT, smp_processor_id());
> (gdb) lx-symbols
> loading vmlinux
> scanning for modules in /home/stefano/repos/linux_vsock/build-tiny-config
> loading @0xffffffffc0169000: /home/stefano/repos/linux_vsock/build-tiny-config/drivers/net/tun.ko
> Traceback (most recent call last):
> File "/home/stefano/repos/linux_vsock/build-tiny-config/scripts/gdb/linux/symbols.py", line 174, in invoke
> self.load_all_symbols()
> File "/home/stefano/repos/linux_vsock/build-tiny-config/scripts/gdb/linux/symbols.py", line 161, in load_all_symbols
> [self.load_module_symbols(module) for module in module_list]
> File "/home/stefano/repos/linux_vsock/build-tiny-config/scripts/gdb/linux/symbols.py", line 161, in <listcomp>
> [self.load_module_symbols(module) for module in module_list]
> File "/home/stefano/repos/linux_vsock/build-tiny-config/scripts/gdb/linux/symbols.py", line 131, in load_module_symbols
> sections=self._section_arguments(module))
> File "/home/stefano/repos/linux_vsock/build-tiny-config/scripts/gdb/linux/symbols.py", line 98, in _section_arguments
> section_name_to_address = {
> File "/home/stefano/repos/linux_vsock/build-tiny-config/scripts/gdb/linux/symbols.py", line 99, in <dictcomp>
> attrs[n]['name'].string(): attrs[n]['address']
> gdb.error: There is no member named name.
> Error occurred in Python: There is no member named name.
>
> I'll try to bisect.
Dig for changes in the data structure (module_sect_attr).
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-07-22 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 9:13 scripts/gdb: received an error when invoking lx-symbols Stefano Garzarella
2020-07-22 9:19 ` Jan Kiszka [this message]
2020-07-22 10:02 ` Stefano Garzarella
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=04728663-acde-bfb7-84dc-f97d628bc739@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sgarzare@redhat.com \
/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