Issue #306 invalid

First level of stack is skipped

Greg Toombs
created an issue

Due to tracer.c:148 and tracer.c:412, when using the API, all code on the same level of the stack as start() is untraced. The workaround is to put anything you need traced at least one function call deep.

Comments (3)

  1. Ned Batchelder repo owner

    Greg Toombs did you try changing those lines? I'm not sure you are correct: I think it is something in CPython's ceval.c that requires the code to be called in a function, and that this happens with the PyTracer trace function also.

  2. Log in to comment