Steve Dower added the comment: At least define EvalFrameEx in a header as an inline func, rather than copying the body.
VS expected to walk the native stack and locate the f parameter in EvalFrameEx. Since the function gets inlined, it couldn't find the frame. I use the JIT hook to insert my own frame onto the stack which is easier to find, so yes, the debugger has been fixed, yes the function gets inlined, and yes this has an impact other than performance. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28924> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
