09-25-2022, 05:34 PM
My $0.02. Be glad we don't have to use "GDB", as in starting it in a terminal to watch any variables or to step through code. Try using Freebasic before it "hit version 1" which was cool only because within "GDB" it was able to display BASIC program code while stepping through it. But that was all. I didn't want to use that program at all. There was an impressive effort by somebody, which was a debugger for Freebasic programs but it was clunky to me, the GUI had too many elements that couldn't be hidden temporarily, but it allowed watching variables and setting breakpoints. Another program was a front end to "GDB", but it was probably the same one I described previously.
I would have used something like Power C Trace which I had to purchase along with Multi-C library and with the license for Power C (including C-library source code) by Mix Software. Although it was taxing sometimes to use Power C Trace: sometimes the user's program ended and therefore had to fire up that debugger again with the user program. Also got tired easily trying to check out something in a function and needing to step through its four or five lines of code about a hundred times...
QB64-created programs could fight with each other to get the focus, especially on Windows. It was that way during v0.98 but I'm not sure if it behaved like that with SDL version. It's a side-effect of "_AUTODISPLAY" mechanism.
I would have used something like Power C Trace which I had to purchase along with Multi-C library and with the license for Power C (including C-library source code) by Mix Software. Although it was taxing sometimes to use Power C Trace: sometimes the user's program ended and therefore had to fire up that debugger again with the user program. Also got tired easily trying to check out something in a function and needing to step through its four or five lines of code about a hundred times...
QB64-created programs could fight with each other to get the focus, especially on Windows. It was that way during v0.98 but I'm not sure if it behaved like that with SDL version. It's a side-effect of "_AUTODISPLAY" mechanism.