The C-BSP interpreter already includes a -t option which makes the interpreter generate a detailed execution trace on standard error. This may be sufficient to diagnose most issues that may arise with BSP scripts (or the interpreter itself), but it is hardly convenient to use. A more expedient diagnostic tool may be desired.
At one point I explored integrating an interactive debugger command-line (in the style of gdb or DEBUG.COM) into the interpreter. I abandoned the feature before submitting the project to GitHub, mostly out of architectural concerns and because robust command line parsing in C was proving to be quite burdensome. Nevertheless I still think this functionality would be useful.
The C-BSP interpreter already includes a
-toption which makes the interpreter generate a detailed execution trace on standard error. This may be sufficient to diagnose most issues that may arise with BSP scripts (or the interpreter itself), but it is hardly convenient to use. A more expedient diagnostic tool may be desired.At one point I explored integrating an interactive debugger command-line (in the style of gdb or DEBUG.COM) into the interpreter. I abandoned the feature before submitting the project to GitHub, mostly out of architectural concerns and because robust command line parsing in C was proving to be quite burdensome. Nevertheless I still think this functionality would be useful.