You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I hinted at in #22 (comment), my use of breakpoint() to enter the debugger seems to be causing a strange error on termination. It seems similar to the issue fixed in 68474af, as it points at a tracer.py line with inspect.currentframe with an AttributeError for that access. No such error appears if I debug using the trepan3k binary.
The text was updated successfully, but these errors were encountered:
I have notice problems in not proper package namespace isolation in one of the packages, but I never had the time to track down or fix. And it might be something altogether different.
Overall nowadays, even though I use these debuggers personally a lot, I don't have time to it the attention it deserves. But it is open source so that means if others want to investigate or contribute they have full reign to do so.
Understood. I tend to throw these issues up as much as engineering notebook entries for myself as requests for help (though since it doesn't seem to break debugging it might languish in my list of priorities, too!)
As I hinted at in #22 (comment), my use of
breakpoint()
to enter the debugger seems to be causing a strange error on termination. It seems similar to the issue fixed in 68474af, as it points at atracer.py
line withinspect.currentframe
with an AttributeError for that access. No such error appears if I debug using thetrepan3k
binary.The text was updated successfully, but these errors were encountered: