New submission from Xavier de Gaye <xdeg...@gmail.com>: In _PyEval_EvalFrameDefault(), the call to maybe_dtrace_line() sets frame->f_lasti to instr_prev and for that reason, in the ensuing call to maybe_call_line_trace(), the call_trace() function with PyTrace_LINE is not called as it should when a backward jump is not to the first instruction of the line.
---------- components: Interpreter Core messages: 314408 nosy: lukasz.langa, serhiy.storchaka, xdegaye priority: normal severity: normal stage: needs patch status: open title: line traces may be missed on backward jumps when instrumented with dtrace type: behavior versions: Python 3.8 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33137> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
