rocky
"Weird termination bug" occurring inconsistently.
As I hinted at in https://github.com/rocky/python3-trepan/issues/22#issuecomment-1219634096, 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 68474af585b7a1c4547ba912feb9c72cfb3cae42, 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 traceback seems to be related to where exactly I break (I only have a very rough idea so far, but breaking early seems to cause it).
The code appears to be visiting both logging/__init__.py in my global Python install and tracer.py in the virtual environment.
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!)