It should be possible to add gdb line mapping with `#line` directives in the output, I think. With a little work, it should also be possible to support inspecting Torque variables, instead of having to inspect registers and figure out what refers to what, and calculating on-stack variables yourself.
In the past, debugging CSA code was mostly (at least for me), done using a combination of the DebugBreak() macro to produce int3 on x86, and the Print() macros for printf-style debugging. Since Torque is just a DSL for creating CSA builtins, the same approach should still work. It’s just a bit more of a headache than having better debugger integration would be.