Message310393
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 |
|
Date |
User |
Action |
Args |
2018-01-22 03:06:04 | xiang.zhang | set | recipients:
+ xiang.zhang, gvanrossum, nedbat, ionelmc, docs@python, raylu |
2018-01-22 03:06:04 | xiang.zhang | set | messageid: <1516590364.75.0.467229070634.issue17799@psf.upfronthosting.co.za> |
2018-01-22 03:06:04 | xiang.zhang | link | issue17799 messages |
2018-01-22 03:06:03 | xiang.zhang | create | |
|