[docs] [issue17799] settrace docs are wrong about "c_call" events

Xiang Zhang report at bugs.python.org
Sun Jan 21 22:06:04 EST 2018

Xiang Zhang <angwerzx at 126.com> added the comment:

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

versions: +Python 3.6, Python 3.7 -Python 3.4, Python 3.5

Python tracker <report at bugs.python.org>

More information about the docs mailing list