From: Kieran Bingham <kieran.bingham@linaro.org>
To: Jan Kiszka <jan.kiszka@web.de>, linux-kernel@vger.kernel.org
Cc: peter.griffin@linaro.org, lee.jones@linaro.org, maxime.coquelin@st.com
Subject: Re: [PATCH 1/2] scripts/gdb: Add version command
Date: Sat, 9 Jan 2016 16:29:20 +0000 [thread overview]
Message-ID: <56913560.9040002@linaro.org> (raw)
In-Reply-To: <56912F22.3030506@web.de>
Hi Jan
On 09/01/16 16:02, Jan Kiszka wrote:
> On 2016-01-07 13:52, Kieran Bingham wrote:
>> lx-version Report the Linux Version of the current kernel.
>>
>> Add a command to identify the version specified by the banner in the
>> debugged kernel.
>>
>> This lets the user identify the kernel of the running kernel, and will
>> let later scripts compare the banner of the attached kernel against the
>> banner in the vmlinux symbols files to verify that the files are correct.
>>
>> Signed-off-by: Kieran Bingham <kieran.bingham@linaro.org>
>> ---
>> scripts/gdb/linux/proc.py | 27 +++++++++++++++++++++++++++
>> scripts/gdb/vmlinux-gdb.py | 1 +
>> 2 files changed, 28 insertions(+)
>> create mode 100644 scripts/gdb/linux/proc.py
>>
>> diff --git a/scripts/gdb/linux/proc.py b/scripts/gdb/linux/proc.py
>> new file mode 100644
>> index 000000000000..7a2afe60416a
>> --- /dev/null
>> +++ b/scripts/gdb/linux/proc.py
>> @@ -0,0 +1,27 @@
>> +#
>> +# gdb helper commands and functions for Linux kernel debugging
>> +#
>> +# Kernel proc information reader
>> +#
>> +# Copyright (c) 2016 Linaro Ltd
>> +#
>> +# Authors:
>> +# Kieran Bingham <kieran.bingham@linaro.org>
>> +#
>> +# This work is licensed under the terms of the GNU GPL version 2.
>> +#
>> +
>> +import gdb
>> +
> pep8 says:
>
> scripts/gdb/linux/proc.py:16:1: E302 expected 2 blank lines, found 1
My apologies - I should have run those checks before I sent the patches.
I've added it to my checklist, to make sure I do, for any more that I send.
>
>> +class LxVersion(gdb.Command):
>> + """ Report the Linux Version of the current kernel.
>> + Equivalent to cat /proc/version on a running target
>> + """
> Minor thing, but for the sake of consistency: Moving the """ into a new
> line gives an additional empty line at the end of the help output. Other
> commands, also gdb built-ins, don't do this.
And, I'll try to make sure I copy the style correctly for any follow-ups!
>
>> + def __init__(self):
>> + super(LxVersion, self).__init__("lx-version", gdb.COMMAND_DATA)
>> +
>> + def invoke(self, arg, from_tty):
>> + # linux_banner should contain a newline
>> + gdb.write(gdb.parse_and_eval("linux_banner").string())
>> +
>> +LxVersion()
>> diff --git a/scripts/gdb/vmlinux-gdb.py b/scripts/gdb/vmlinux-gdb.py
>> index ce82bf5c3943..d5943eca19cd 100644
>> --- a/scripts/gdb/vmlinux-gdb.py
>> +++ b/scripts/gdb/vmlinux-gdb.py
>> @@ -29,3 +29,4 @@ else:
>> import linux.tasks
>> import linux.cpus
>> import linux.lists
>> + import linux.proc
>>
> Two options: I can adjust these (and the corresponding issues in patch
> 2) myself before sending out a merge request to Andrew. Or, if you have
> more in your queue, I'll wait for a potential longer v2 round. Just let
> me know.
>
> Thanks,
> Jan
If you're happy to do the fix-ups that's fine by me.
These two are simple and standalone, so I don't see any point in holding
them back.
--
Regards
Kieran
next prev parent reply other threads:[~2016-01-09 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 12:52 [PATCH 0/2] Linux Kernel Debugger GDB extensions Kieran Bingham
2016-01-07 12:52 ` [PATCH 1/2] scripts/gdb: Add version command Kieran Bingham
2016-01-09 16:02 ` Jan Kiszka
2016-01-09 16:29 ` Kieran Bingham [this message]
2016-01-07 12:52 ` [PATCH 2/2] scripts/gdb: Add cmdline reader command Kieran Bingham
-- strict thread matches above, loose matches on Subject: below --
2016-01-11 10:47 [PATCH 0/2] scripts/gdb: Updates for 4.5 Jan Kiszka
2016-01-11 10:47 ` [PATCH 1/2] scripts/gdb: Add version command Jan Kiszka
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=56913560.9040002@linaro.org \
--to=kieran.bingham@linaro.org \
--cc=jan.kiszka@web.de \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.coquelin@st.com \
--cc=peter.griffin@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