[issue29680] gdb/libpython.py does not work with gdb 7.2

2017-03-27 Thread STINNER Victor
STINNER Victor added the comment: @belopolsky: Tools/gdb/libpython.py still uses gdb.error in gdb.selected_frame(): try: frame = cls.get_selected_frame() except gdb.error: # No frame: Python didn't start yet return None See my commit

[issue29680] gdb/libpython.py does not work with gdb 7.2

2017-03-24 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: New changeset 661ca8843fed1183e38db06e52d59ac300bf1c2a by Lev Abalkin in branch 'master': Fixes bpo-29680: Older gdb does not have gdb.error. (#363) https://github.com/python/cpython/commit/661ca8843fed1183e38db06e52d59ac300bf1c2a --

[issue29680] gdb/libpython.py does not work with gdb 7.2

2017-03-24 Thread Mariatta Wijaya
Mariatta Wijaya added the comment: PR has been merged and backported into 3.6. If there is nothing else, please close this :) Thanks. -- ___ Python tracker

[issue29680] gdb/libpython.py does not work with gdb 7.2

2017-03-24 Thread Mariatta Wijaya
Mariatta Wijaya added the comment: New changeset 23b26c4e206427a9e0a1d39240c17a049cf8c732 by Mariatta in branch '3.6': Fixes bpo-29680: Older gdb does not have gdb.error. (GH-363) (GH-534) https://github.com/python/cpython/commit/23b26c4e206427a9e0a1d39240c17a049cf8c732 -- nosy:

[issue29680] gdb/libpython.py does not work with gdb 7.2

2017-03-06 Thread Mariatta Wijaya
Changes by Mariatta Wijaya : -- pull_requests: +442 ___ Python tracker ___ ___

[issue29680] gdb/libpython.py does not work with gdb 7.2

2017-03-01 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Victor, the gdb commit that you mentioned introduced gdb.GdbError which is different from gdb.error. [1] The correct commit is 621c83642d17cf523c20f55f2ed945a7ec95ea6a. [2] [1]

[issue29680] gdb/libpython.py does not work with gdb 7.2

2017-03-01 Thread STINNER Victor
STINNER Victor added the comment: It's a regression introduced in Python 3.6 by CPython change: https://github.com/python/cpython/commit/d7d2bc8798da3b083e383e949ba01d61b78e4e4d gdb.error was introduced in gdb 7.3 by the commit 07ca107c2d958b45633ef0cdcce7219a95f0cf01:

[issue29680] gdb/libpython.py does not work with gdb 7.2

2017-02-28 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- components: +Demos and Tools stage: -> patch review ___ Python tracker ___

[issue29680] gdb/libpython.py does not work with gdb 7.2

2017-02-28 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- pull_requests: +308, 309 ___ Python tracker ___

[issue29680] gdb/libpython.py does not work with gdb 7.2

2017-02-28 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- pull_requests: +308 ___ Python tracker ___

[issue29680] gdb/libpython.py does not work with gdb 7.2

2017-02-28 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- nosy: +haypo ___ Python tracker ___ ___

[issue29680] gdb/libpython.py does not work with gdb 7.2

2017-02-28 Thread Alexander Belopolsky
New submission from Alexander Belopolsky: Printing the backtrace in gdb results in Python errors: (gdb) bt ... #6 0x77ba9745 in _PyEval_EvalCodeWithName (_co=, globals=Traceback (most recent call last): File "/home/a/.virtualenvs/3.6g/bin/python3.6-gdb.py", line 1358, in to_string