Dom has reported and fixed an issue in using the lx-dmesg command when gdb is built against a Python 3 interpreter. He has provided a fix which is compatible for both Python 2 and 3, which has been tested accordingly.
The Python 3 interpreter represents byte streams with a b'<text>' marker, which I think could be handled by the gdb.write() function, but until that is adapted we can '.decode()' the string so that it is handled as expected. This is still compatible with both Python 2 and 3. I have run pep8, and performed a test merge against linux-next. These could be classed as fixes for 4.6, but I suspect we may be nearing the end of that window of opportunity as I see the AKPM branch has already gone in for this release. As this is not a regression, I don't think it will be any great harm if this slips to 4.7, but 4.6 will be a bonus, or we could aim for the stable trees. If you prefer to pull, a signed tag is available at: https://github.com/kbingham/linux.git v4.6-rc6-dmesg-fix Dom Cote (2): scripts/gdb: Improve types abstraction for gdb python scripts scripts/gdb: Fix issue with dmesg.py and python 3.X Kieran Bingham (1): scripts/gdb: decode bytestream on dmesg for Python3 scripts/gdb/linux/dmesg.py | 11 ++++++----- scripts/gdb/linux/utils.py | 17 +++++++++++++++-- 2 files changed, 21 insertions(+), 7 deletions(-) -- 2.5.0
