[issue30983] eval frame rename in pep 0523 broke gdb's python extension

2017-07-21 Thread Bruno Penteado
Changes by Bruno Penteado <pol...@gmail.com>: -- pull_requests: +2853 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30983> ___ _

[issue30983] eval frame rename in pep 0523 broke gdb's python extension

2017-07-21 Thread Bruno Penteado
Changes by Bruno Penteado <pol...@gmail.com>: -- 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 <rep...@bugs.python.org> <http

[issue30983] eval frame rename in pep 0523 broke gdp's python extension

2017-07-21 Thread Bruno Penteado
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