[issue29673] Some gdb macros are broken in 3.6

[Marcel Plch]

Marcel Plch <gmarcel.plch at gmail.com> added the comment:

I have created a PR here - https://github.com/python/cpython/pull/6126

The problem was, indeed, change in the code structure. The macro checked for presence inside of PyEval_EvalFrame() using address of a neighbouring function.
Also, arguments to PyEval_EvalFrame() were changed, so the macro responsible for printing of the frame needed a little tweak.

----------
nosy: +Dormouse759

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29673>
_______________________________________