public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Nikolay Borisov <n.borisov.lkml@gmail.com>
Cc: linux-kernel@vger.kernel.org, Kieran Bingham <kieran@ksquared.org.uk>
Subject: Re: [PATCH] scripts/gdb: Add automatic path expansion when loading modules
Date: Wed, 8 Jun 2016 12:21:50 +0200	[thread overview]
Message-ID: <5757F1BE.703@siemens.com> (raw)
In-Reply-To: <5757EEC1.6000309@gmail.com>

On 2016-06-08 12:09, Nikolay Borisov wrote:
> 
> 
> On 06/08/2016 12:35 PM, Jan Kiszka wrote:
>> On 2016-06-07 23:26, Nikolay Borisov wrote:
>>> Python doesn't do automatic expansion of paths. In case one passes
>>> path of the from ~/foo/bar the gdb scripts won't automatically expand
>>> that and as a result the symbols files won't be loaded. Fix this
>>> by explicitly expanding all paths which begin with "~"
>>>
>>> Signed-off-by: Nikolay Borisov <n.borisov.lkml@gmail.com>
>>> ---
>>>  scripts/gdb/linux/symbols.py | 7 +++++++
>>>  1 file changed, 7 insertions(+)
>>>
>>> diff --git a/scripts/gdb/linux/symbols.py b/scripts/gdb/linux/symbols.py
>>> index 9a0f8923f67c..2f5b2bee8c34 100644
>>> --- a/scripts/gdb/linux/symbols.py
>>> +++ b/scripts/gdb/linux/symbols.py
>>> @@ -81,6 +81,12 @@ lx-symbols command."""
>>>                          self.module_files.append(root + "/" + name)
>>>          self.module_files_updated = True
>>>  
>>> +    def __expand_homedir(self):
>>> +        for index, path in enumerate(self.module_paths):
>>> +            if path.startswith("~"):
>>> +                self.module_paths[index] = os.path.expanduser(path)
>>> +
>>> +
>>>      def _get_module_file(self, module_name):
>>>          module_pattern = ".*/{0}\.ko$".format(
>>>              module_name.replace("_", r"[_\-]"))
>>> @@ -160,6 +166,7 @@ lx-symbols command."""
>>>          self.module_files = []
>>>          self.module_files_updated = False
>>>  
>>> +        self.__expand_homedir()
>>>          self.load_all_symbols()
>>>  
>>>          if hasattr(gdb, 'Breakpoint'):
>>>
>>
>> Valid point, but let's expand unconditionally in invoke when building
>> self.module_paths.
>>
>> I'm no Python expert, but my feeling tells me that there is even a more
>> compact way to do loop. Does this work?
>>
>> module_paths = [expanduser(p) for p in arg.spilt()]
> 
> module_paths = [os.path.expanduser(p) for p in arg.spilt()] does work.
> 
> I'm no python expert either, but list comprehensions is more idiomatic
> indeed. I will cook up a patch tonight and resend, unless you want to do
> it.

Go ahead, looking forward to your patch!

Thanks
Jan

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

  reply	other threads:[~2016-06-08 10:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07 21:26 [PATCH] scripts/gdb: Add automatic path expansion when loading modules Nikolay Borisov
2016-06-08  9:35 ` Jan Kiszka
2016-06-08 10:09   ` Nikolay Borisov
2016-06-08 10:21     ` Jan Kiszka [this message]
2016-06-08 16:28       ` [PATCH] scripts/gdb: Perform path expansion to lx-symbol's arguments Nikolay Borisov
2016-06-13  6:18         ` Jan Kiszka
2016-06-13  8:54           ` 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=5757F1BE.703@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=kieran@ksquared.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=n.borisov.lkml@gmail.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