Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New issue] traceback events are sometimes missing their f_back pointer
----------------------------------------------
ISSUES
1. [New issue] traceback events are sometimes missing their f_back pointer
http://ironpython.codeplex.com/workitem/31437
User dinov has proposed the issue:
"This repro requires Scipy.net:
import thread
print "Running on thread", thread.get_ident()
class C(object):
def trace_func(self, frame, event, arg):
if event == 'return':
if frame.f_back is None:
print 'no back frame', thread.get_ident()
return self.trace_func
import sys
sys.settrace(C().trace_func)
import scipy
This will setup the trace function on the thread and then import scipy.
Eventually we get to a point where there is no back frame on a return event -
but one must exist because our top-level module code is still running. This
can break debuggers built on top of sys.settrace"
----------------------------------------------
----------------------------------------------
You are receiving this email because you subscribed to notifications on
CodePlex.
To report a bug, request a feature, or add a comment, visit IronPython Issue
Tracker. You can unsubscribe or change your issue notification settings on
CodePlex.com._______________________________________________
Ironpython-users mailing list
Ironpython-users@python.org
http://mail.python.org/mailman/listinfo/ironpython-users
