Is there any other way to debug swig extensions besides doing
gdb python stuff.py
?
I wrapped the obsolete libkdtree ++ library and executed all swig-related memory management points (borrowed ref or native ref, etc.). But still, I'm not sure if my memory attachment is tied. It would be useful to be able to simply debug every step-by-step published function: starting with Python, then going through binding glue C to space C and going back.
Is there such an opportunity?
source
share