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 lukasz.langa
Recipients bcap, cooperlees, lukasz.langa, vstinner
Date 2017-08-18.23:31:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1503099113.66.0.660403856325.issue30983@psf.upfronthosting.co.za>
In-reply-to
Content
The issue originally stems from the fact that a non-debug Python build with --enable-shared is inlining PyEval_EvalFrameEx into _PyEval_EvalFrameDefault.

So, the patch should really become to *replace* discovering PyEval_EvalFrameEx with the discovery of _PyEval_EvalFrameDefault. This might be problematic in the future when there is an actual JIT but currently it's strictly better than the current situation where the gdb bindings simply don't work for shared builds.
History
Date User Action Args
2017-08-18 23:31:53lukasz.langasetrecipients: + lukasz.langa, vstinner, cooperlees, bcap
2017-08-18 23:31:53lukasz.langasetmessageid: <1503099113.66.0.660403856325.issue30983@psf.upfronthosting.co.za>
2017-08-18 23:31:53lukasz.langalinkissue30983 messages
2017-08-18 23:31:53lukasz.langacreate