Author xdegaye
Recipients xdegaye
Date 2014-03-23.08:36:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1395563773.85.0.562245931726.issue21033@psf.upfronthosting.co.za>
In-reply-to
Content
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
2014-03-23 08:36:13xdegayesetrecipients: + xdegaye
2014-03-23 08:36:13xdegayesetmessageid: <1395563773.85.0.562245931726.issue21033@psf.upfronthosting.co.za>
2014-03-23 08:36:13xdegayelinkissue21033 messages
2014-03-23 08:36:13xdegayecreate