All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kieran Bingham <kieran@ksquared.org.uk>
To: buzdelabuz2@gmail.com, jan.kiszka@siemens.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Improve types abstraction for gdb python scripts
Date: Wed, 4 May 2016 13:37:01 +0100	[thread overview]
Message-ID: <5729ECED.7090708@bingham.xyz> (raw)
In-Reply-To: <1462331576-5570-1-git-send-email-buzdelabuz2+git@gmail.com>

On 04/05/16 04:12, buzdelabuz2@gmail.com wrote:
> From: Dom Cote <buzdelabuz2+git@gmail.com>
> 
> Change the read_u16 function so it accepts both 'str' and 'byte'
> as type for the arguments.
> 
> When calling read_memory() from gdb API, depending on if
> it was built with 2.7 or 3.X, the format used to return the
> data will differ ( 'str' for 2.7, and 'byte' for 3.X ).
> 
> Add a function read_memoryview() to be able to get a
> 'memoryview' object back from read_memory() both with
> python 2.7 and 3.X .
> 
> Tested with python 3.4 and 2.7
> Tested with gdb 7.7

I have also tested with Python 3.4, 2.7 on GDB 11

> 
> Signed-off-by: Dom Cote <buzdelabuz2+git@gmail.com>

Acked-by: Kieran Bingham <kieran@bingham.xyz>
Tested-by: Kieran Bingham <kieran@bingham.xyz>

> ---
>  scripts/gdb/linux/utils.py | 17 +++++++++++++++--
>  1 file changed, 15 insertions(+), 2 deletions(-)
> 
> diff --git a/scripts/gdb/linux/utils.py b/scripts/gdb/linux/utils.py
> index 0893b326a28b..dba6c88ea7b9 100644
> --- a/scripts/gdb/linux/utils.py
> +++ b/scripts/gdb/linux/utils.py
> @@ -87,11 +87,24 @@ def get_target_endianness():
>      return target_endianness
>  
>  
> +def read_memoryview(inf, start, length):
> +    return memoryview(inf.read_memory(start, length))
> +
> +
>  def read_u16(buffer):
> +    value = [0, 0]
> +
> +    if type(buffer[0]) is str:
> +        value[0] = ord(buffer[0])
> +        value[1] = ord(buffer[1])
> +    else:
> +        value[0] = buffer[0]
> +        value[1] = buffer[1]
> +
>      if get_target_endianness() == LITTLE_ENDIAN:
> -        return ord(buffer[0]) + (ord(buffer[1]) << 8)
> +        return value[0] + (value[1] << 8)
>      else:
> -        return ord(buffer[1]) + (ord(buffer[0]) << 8)
> +        return value[1] + (value[0] << 8)
>  
>  
>  def read_u32(buffer):
> 

-- 
Regards

Kieran Bingham

  parent reply	other threads:[~2016-05-04 12:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-04  3:12 [PATCH 1/2] Improve types abstraction for gdb python scripts buzdelabuz2
2016-05-04  3:12 ` [PATCH 2/2] Fix issue with dmesg.py and python 3.X buzdelabuz2
2016-05-04  5:41   ` Jan Kiszka
2016-05-04 12:37   ` Kieran Bingham
2016-05-04 12:37   ` [PATCH] scripts/gdb: decode bytestream on dmesg for Python3 Kieran Bingham
2016-05-05 14:20     ` Dom Cote
2016-05-04 12:37 ` Kieran Bingham [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-05-04  3:08 [PATCH 1/2] Improve types abstraction for gdb python scripts buzdelabuz2

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=5729ECED.7090708@bingham.xyz \
    --to=kieran@ksquared.org.uk \
    --cc=buzdelabuz2@gmail.com \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.