We have a rather large and complex Python program which has many SWIG-wrapped C/C++ parts as well.
After attempting to implement a new part of this system, I keep hitting "Fatal Python error: GC object already tracked" and then a segmentation fault.
This occurs with regularity on Linux (64-bit OS/app) and Windows 10 (32-bit OS/app)
I've looked all over the web, have played with gdb backtraces on the coredumps, using Python's own gc module inspection, and sys.settrace(), valgrind, and more and after several days have still not managed to get any closer to working out WHAT the object that is already tracked is.
Why doesn't Python tell us this information?
Is there any way I can try and find out WHAT the object is that's causing this fatal error, so I can correct my code to behave correctly?