➜

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.

classification
Title: line traces may be missed on backward jumps when instrumented with dtrace
Type: behavior Stage: needs patch
Components: Interpreter Core Versions: Python 3.8
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: lukasz.langa, serhiy.storchaka, xdegaye
Priority: normal Keywords:

Created on 2018-03-25 12:01 by xdegaye, last changed 2022-04-11 14:58 by admin.

Messages (1)
msg314408 - (view) Author: Xavier de Gaye (xdegaye) * (Python triager) Date: 2018-03-25 12:01 
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.
History
Date User Action Args
2022-04-11 14:58:59adminsetgithub: 77318
2018-03-25 12:01:28xdegayecreate