➜

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: previous trace function still invoked after sys.settrace()
Type: behavior Stage:
Components: Interpreter Core Versions: Python 3.5
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: xdegaye
Priority: normal Keywords:

Created on 2014-03-23 08:36 by xdegaye, last changed 2022-04-11 14:58 by admin.

Files
File name Uploaded Description Edit
settrace.py xdegaye, 2014-03-23 08:36
Messages (1)
msg214553 - (view) Author: Xavier de Gaye (xdegaye) * (Python triager) Date: 2014-03-23 08:36 
The following output of settrace.py shows that the Tracer trace function is still called in foo() after the New_tracer trace function has been installed with sys.settrace() from within the trace function itself, and even though f_trace has been set on all the frames of the stack with the new trace function as this is done in bdb.Bdb.set_trace():

sys.settrace(Tracer.trace)
Tracer:line at <module>:30
Tracer:call at foo:23
sys.settrace(New_tracer.trace)
Tracer:line at foo:24
New_tracer:call at bar:27
New_tracer:line at bar:27
New_tracer:return at bar:27
Tracer:line at foo:25
Tracer:return at foo:25
New_tracer:return at <module>:30

Python should not allow to call successfully sys.settrace() when tracing, except for sys.settrace(None).
This does not seem easy to fix without adding some state, as the 'tracing' field in PyThreadState is used for both trace/profile codes.
History
Date User Action Args
2022-04-11 14:58:00adminsetgithub: 65232
2014-03-23 08:36:13xdegayecreate