[issue31344] f_trace_opcodes frame attribute to switch to per-opcode tracing

Changes by Nick Coghlan : -- resolution: -> fixed stage: commit review -> resolved status: open -> closed ___ Python tracker ___

[issue31344] f_trace_opcodes frame attribute to switch to per-opcode tracing

Nick Coghlan added the comment: New changeset 5a8516701f5140c8c989c40e261a4f4e20e8af86 by Nick Coghlan in branch 'master': bpo-31344: Per-frame control of trace events (GH-3417) https://github.com/python/cpython/commit/5a8516701f5140c8c989c40e261a4f4e20e8af86 --

[issue31344] f_trace_opcodes frame attribute to switch to per-opcode tracing

Nick Coghlan added the comment: My posted PR implements the "independent flags" option, where f_trace_lines and f_trace_opcodes allow per-line and per-opcode events to be requested independently. The default is to emit per-line events (as has historically been the case). -- stage:

[issue31344] f_trace_opcodes frame attribute to switch to per-opcode tracing

Changes by Nick Coghlan : -- pull_requests: +3415 ___ Python tracker ___ ___

[issue31344] f_trace_opcodes frame attribute to switch to per-opcode tracing

Changes by Nick Coghlan : -- assignee: -> ncoghlan ___ Python tracker ___ ___

[issue31344] f_trace_opcodes frame attribute to switch to per-opcode tracing

Changes by Nick Coghlan : -- nosy: +steve.dower ___ Python tracker ___ ___

[issue31344] f_trace_opcodes frame attribute to switch to per-opcode tracing

Nick Coghlan added the comment: Steve's also requested the ability to *turn off* line debugging, and I'm thinking it may make sense to allow all four configurations: * both line and opcode events disabled * only getting one or the other * getting both kinds of event Opcode events would

[issue31344] f_trace_opcodes frame attribute to switch to per-opcode tracing

Nathaniel Smith added the comment: Adding Ned to CC in case he wants to comment on the utility of per-opcode tracing from the perspective of coverage.py. -- nosy: +nedbat, njs ___ Python tracker

[issue31344] f_trace_opcodes frame attribute to switch to per-opcode tracing

Serhiy Storchaka added the comment: The f_trace attribute is writable from a tracing function. There are different restrictions, for example you can't jump inside a 'for' loop from outside. The code of the setter is complex and hard for modifications (see the discussion on PR 2827). Allowing

[issue31344] f_trace_opcodes frame attribute to switch to per-opcode tracing

New submission from Nick Coghlan: In order to test issue 29988 reliably, we want the ability to run trace hooks for every opcode in a frame, rather than for every line. The simplest API we've been able to come up with for that is a "f_trace_opcodes" attribute on the frame which we set from