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 xiang.zhang
Recipients docs@python, gvanrossum, ionelmc, nedbat, raylu, xiang.zhang
Date 2018-01-22.03:06:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1516590364.75.0.467229070634.issue17799@psf.upfronthosting.co.za>
In-reply-to
Content
Hi Guido. Looking at the implementation, it seems pdb ignores c_call not by relying on the interpreter, but bdb takes no action when encountering C events. Yeah, even bdb wrongly expects C events will be triggered for settrace. [1]

And what if some debuggers want not only to trace Python events but also C events, then it has to mix the power of trace and profile but can't only rely on trace.

[1] https://github.com/python/cpython/blob/master/Lib/bdb.py#L59
History
Date User Action Args
2018-01-22 03:06:04xiang.zhangsetrecipients: + xiang.zhang, gvanrossum, nedbat, ionelmc, docs@python, raylu
2018-01-22 03:06:04xiang.zhangsetmessageid: <1516590364.75.0.467229070634.issue17799@psf.upfronthosting.co.za>
2018-01-22 03:06:04xiang.zhanglinkissue17799 messages
2018-01-22 03:06:03xiang.zhangcreate