Program line

[Chris]

Hello. I don't know if I'm repeating myself. Is it possible to observe the execution of a program in QB64 step by step like it was in the historical Qbasic. Each line of the program was highlighted.
Best regards - Chris

[SMcNeill]

You would need to enable the debugger in the menu and use it.

[Pete]

https://qb64phoenix.com/qb64wiki/index.php/%24DEBUG

I'd tell you more about it, but I don't use it.... because I never make mistakes. Yeah let's go with that!

Pete

[bplus]

I don't use it either, not that I don't make mistakes. I makes so many mistakes that I have developed my own habits of debugging long before Debug for QB64 rolled into town only a few years ago. These habits work in several Basics.

[Pete]

I'll +1 that for honesty... and dammit because I'm also going to use that explanation from now on, because that's exactly what I did before the DEBUG period, too. I think seven or so years back I even partly made a trace program to trace program flow. Same concept as the DEBUG project, but without TCP/IP communications.

Pete

[hsiangch_ong]

i got very spoiled by the qb45 debugger.  but none of my programs were very complex.  all my games in the early 1990s used key on/off/stop interrupts.  i didn't have a good experience with inkey$ while on basica.  because ibm pc and work-alikes possessed a keystroke buffer.  different from the function of many 8-bit computers with built-in basic.

i have never used the "debugger" in qb64.  probably never will.  the "g++" works very slowly already.  i don't want to make it even slower.  even on internal ssd.  it's not going to catch that great bug i always develop in every program.  which is a misplaced variable.  or which should have had a better name.  or round-off error because the type should have been double instead of _integer64.

highlight statement lines.  i was the proud owner of power c compiler with source code for the libraries.  a library called "multi-c" which faked multithreaded programs on a single-core processor.  never got to use it.  also with this thing called power ctrace.  all from mix software from richardson, texas.  the power ctrace was a debugger.  needed to compile the program with "debug" symbols into an exe file.  then run power ctrace with that exe file as data.  it allowed the user to step through code, forward or backward.  statement by statement, not necessarily line by line.  what was irritating is that if the program ended run.  if the user desired to continue watching things in the program.  then it couldn't be done.  power ctrace had to be started again with the same exe file.

the quickbasic debugger was positively telepathic compared to that, though.

[Chris]

As I see, my program version 1.4 does not support $DEBUG.
Thanks

[Petr]

Yeah, TRON and TROFF are not implemented. Sometimes is good way write array content to file and them look in them. We've seen @FellippeHeitor 's video about the Debug feature in the past - he said something about how easy it is to use - but......

[Pete]

Yeah, TRON and TROFF are not implemented. Sometimes is good way write array content to file and them look in them. We've seen @FellippeHeitor 's video about the Debug feature in the past - he said something about how easy it is to use - but......

 

I struggled trying to use it, too. It's harder to explain things when you are the developer than most think. Familiarity goes a long way. Of course I struggle with "Hello World!" One L or 3?

Pete

(Yes Steve, we know it's 3.... 2 'L's in Hello and 1 in World!)

- I'm on strike, on it's preemptive.

[FellippeHeitor]

How about we arrange an online meeting and I walk you guys through the debugger again? Who’s up for it?