Re: [PATCH] Fix issue with dmesg.py and python 3.X

2016-05-03 Thread Kieran Bingham
On 29/04/16 20:00, Dom Cote wrote: > Hi Kieran, Hi Dom, sorry for the delay, we had a 3 day weekend over here :) > > Thanks for pinging me on this. > > I had to rebuild a version of GDB with python 2.7 (mine system has 3.X). > I had to dig into the configure.ac script to

Re: [PATCH] Fix issue with dmesg.py and python 3.X

2016-05-03 Thread Kieran Bingham
On 29/04/16 20:00, Dom Cote wrote: > Hi Kieran, Hi Dom, sorry for the delay, we had a 3 day weekend over here :) > > Thanks for pinging me on this. > > I had to rebuild a version of GDB with python 2.7 (mine system has 3.X). > I had to dig into the configure.ac script to

Re: [PATCH] Fix issue with dmesg.py and python 3.X

2016-04-29 Thread Kieran Bingham
Hi Dom, On 08/04/16 04:33, Dom Cote wrote: > Hi Kieran, > > Thanks for the feedback. > > I am going to need to build a version of gdb with python 2.7 to see what > the differences are, and try to abstract them in the best possible way. > > Then I will send a new patch and incorporate what you

Re: [PATCH] Fix issue with dmesg.py and python 3.X

2016-04-29 Thread Kieran Bingham
Hi Dom, On 08/04/16 04:33, Dom Cote wrote: > Hi Kieran, > > Thanks for the feedback. > > I am going to need to build a version of gdb with python 2.7 to see what > the differences are, and try to abstract them in the best possible way. > > Then I will send a new patch and incorporate what you

Re: [PATCH] Fix issue with dmesg.py and python 3.X

2016-04-07 Thread Kieran Bingham
Hi Dom, I've just tested your patch quickly, and it generates an error on Python 2.7 On 05/04/16 19:38, Dom Cote wrote: > When using GDB built with python 2.7, > > Inferior.read_memory (address, length) > > returns a buffer object. When using GDB built with python 3.X, > it returns a

Re: [PATCH] Fix issue with dmesg.py and python 3.X

2016-04-07 Thread Kieran Bingham
Hi Dom, I've just tested your patch quickly, and it generates an error on Python 2.7 On 05/04/16 19:38, Dom Cote wrote: > When using GDB built with python 2.7, > > Inferior.read_memory (address, length) > > returns a buffer object. When using GDB built with python 3.X, > it returns a

[PATCH] Fix issue with dmesg.py and python 3.X

2016-04-05 Thread Dom Cote
When using GDB built with python 2.7, Inferior.read_memory (address, length) returns a buffer object. When using GDB built with python 3.X, it returns a memoryview object, which cannot be added to another memoryview object. Replace the addition (+) of 2 python memoryview objects with the

[PATCH] Fix issue with dmesg.py and python 3.X

2016-04-05 Thread Dom Cote
When using GDB built with python 2.7, Inferior.read_memory (address, length) returns a buffer object. When using GDB built with python 3.X, it returns a memoryview object, which cannot be added to another memoryview object. Replace the addition (+) of 2 python memoryview objects with the