public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Daniel Wagner <wagi@monom.org>
Cc: linux-kernel@vger.kernel.org,
	Daniel Wagner <daniel.wagner@bmw-carit.de>,
	Jiri Kosina <jkosina@suse.cz>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Kieran Bingham <kieran.bingham@linaro.org>
Subject: Re: [PATCH] scripts/gdb: Fix loading of modules information
Date: Tue, 29 Mar 2016 09:22:58 +0200	[thread overview]
Message-ID: <56FA2D52.2030402@siemens.com> (raw)
In-Reply-To: <56FA2B31.4040309@monom.org>

On 2016-03-29 09:13, Daniel Wagner wrote:
> On 03/29/2016 08:59 AM, Jan Kiszka wrote:
>> On 2016-03-29 08:41, Daniel Wagner wrote:
>>>          for module in module_list():
>>>              gdb.write("{address} {name:<19} {size:>8}  {ref}".format(
>>> -                address=str(module['module_core']).split()[0],
>>> +                module_layout=module['core_layout']
>>> +                addressr=str(module_layout['base'])
>>
>> This looks untested.
> 
> Yep, I send out the untested version. Need more coffee...
> 
>>>                  name=module['name'].string(),
>>>                  size=str(module['core_size']),
>>>                  ref=str(module['refcnt']['counter'])))
>>> diff --git a/scripts/gdb/linux/symbols.py b/scripts/gdb/linux/symbols.py
>>> index 627750c..8650ede 100644
>>> --- a/scripts/gdb/linux/symbols.py
>>> +++ b/scripts/gdb/linux/symbols.py
>>> @@ -108,7 +108,8 @@ lx-symbols command."""
>>>  
>>>      def load_module_symbols(self, module):
>>>          module_name = module['name'].string()
>>> -        module_addr = str(module['module_core']).split()[0]
>>> +        module_layout = module['core_layout']
>>> +        module_addr = str(module_layout['base'])
>>>  
>>>          module_file = self._get_module_file(module_name)
>>>          if not module_file and not self.module_files_updated:
>>>
>>
>> Thanks, but ad4db3b24a should already be on its way into stable.
> 
> Ah, I haven't got that fix yet because I am still on a older branch.
> Also my google-foo didn't help.
> 
> Sorry about that noise.

No problem. At least we now know another frequent user.

BTW, Kieran and some other people at Linaro started to think about how
to auto-test for such regressions - probably the only reliable way to
catch them.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2016-03-29  7:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29  6:41 [PATCH] scripts/gdb: Fix loading of modules information Daniel Wagner
2016-03-29  6:58 ` [PATCH v2] " Daniel Wagner
2016-03-29  6:59 ` [PATCH] " Jan Kiszka
2016-03-29  7:13   ` Daniel Wagner
2016-03-29  7:22     ` Jan Kiszka [this message]
2016-03-31  6:17       ` Daniel Wagner

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=56FA2D52.2030402@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=daniel.wagner@bmw-carit.de \
    --cc=jkosina@suse.cz \
    --cc=kieran.bingham@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=wagi@monom.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