Debugging is certainly painful even without TG getting in the way. The only crude way to debug actual Kid errors so far is a trial-and-run approach with cutting suspicious blocks of code.
I've documented my experience here: http://max.textdriven.com/blog/entries/69/debugging-kid-templates-and-leaking-abstractions/ Regards, Max.
