Yes, I love it so much, for the Python debugger I prefer pudb, this future
enable up and down the call stack in both Python and C++ code very smoothly,
just like go through the pure C++ program's stack in gdb TUI, so nice.
but I found the RPC exception error message and call stack can be
Note that in the new ffi, we have better backtrace support through lib
backtrace, so right now if an exception is thrown from cxx end, the trace will
be incorporated into the python trace and also clickable if we are in editors
like vscode
```python
from tvm import ffi as tvm_ffi
def error_t
Rencently we upgrade our work on the newest code, honestly it is a hard work to
do it, but it is worth, everybody can gain lots from the new ffi's design and
implementation.
The new ffi drop the ctypes solution, only Cython solution is provided, this
make debug a little harder, now if you wa
