Revert "[3.6] bpo-30983: eval frame rename in pep 0523 broke gdb's python extension (GH-2803) (#3090)" (#3101)
This reverts commit 09b77165e3
.
This commit is contained in:
parent
de36ba065e
commit
98e26979aa
|
@ -1,4 +0,0 @@
|
|||
With PEP 523, gdb's Python integration stopped working properly for frames
|
||||
using the ``_PyEval_EvalFrameDefault`` function. Affected functionality
|
||||
included `py-list` and `py-bt`. This is now fixed. Patch by Bruno "Polaco"
|
||||
Penteado.
|
|
@ -1502,10 +1502,8 @@ class Frame(object):
|
|||
return False
|
||||
|
||||
def is_evalframeex(self):
|
||||
'''Is this a PyEval_EvalFrameEx or _PyEval_EvalFrameDefault (PEP 0523)
|
||||
frame?'''
|
||||
if self._gdbframe.name() in ('PyEval_EvalFrameEx',
|
||||
'_PyEval_EvalFrameDefault'):
|
||||
'''Is this a PyEval_EvalFrameEx frame?'''
|
||||
if self._gdbframe.name() == 'PyEval_EvalFrameEx':
|
||||
'''
|
||||
I believe we also need to filter on the inline
|
||||
struct frame_id.inline_depth, only regarding frames with
|
||||
|
|
Loading…
Reference in New Issue