➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients brett.cannon, dino.viehland, serhiy.storchaka, steve.dower, vstinner
Date 2016-12-15.14:27:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481812055.48.0.292780958718.issue28924@psf.upfronthosting.co.za>
In-reply-to
Content 
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.
History
Date User Action Args
2016-12-15 14:27:35steve.dowersetrecipients: + steve.dower, brett.cannon, vstinner, dino.viehland, serhiy.storchaka
2016-12-15 14:27:35steve.dowersetmessageid: <1481812055.48.0.292780958718.issue28924@psf.upfronthosting.co.za>
2016-12-15 14:27:35steve.dowerlinkissue28924 messages
2016-12-15 14:27:35steve.dowercreate