[issue30983] eval frame rename in pep 0523 broke gdp's python extension
New submission from Bruno Penteado: pep 0523 renames PyEval_EvalFrameEx to _PyEval_EvalFrameDefault while the gdb python extension only looks for PyEval_EvalFrameEx to understand if it is dealing with a frame. Final effect is that attaching gdb to a python3.6 process doesnt resolve python objects. Eg. py-list and py-bt dont work properly -- messages: 298804 nosy: bcap priority: normal severity: normal status: open title: eval frame rename in pep 0523 broke gdp's python extension versions: Python 3.6, Python 3.7 ___ Python tracker <http://bugs.python.org/issue30983> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30983] eval frame rename in pep 0523 broke gdb's python extension
Changes by Bruno Penteado : -- title: eval frame rename in pep 0523 broke gdp's python extension -> eval frame rename in pep 0523 broke gdb's python extension ___ Python tracker <http://bugs.python.org/issue30983> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30983] eval frame rename in pep 0523 broke gdb's python extension
Changes by Bruno Penteado : -- pull_requests: +2853 ___ Python tracker <http://bugs.python.org/issue30983> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
