After years of using the Xojo Debugger for Desktop apps, I realize I’ve learned a few “muscle memory” tricks for avoiding trouble:
don’t have the contents of an Object instance showing after the object goes Nil
don’t view method or window properties when stepping out of a method
These bugs may have been fixed in recent versions, but they are still in my brain.
I realized that in Web apps, I’m developing a new anxiety:
while debugging a web app, don’t stop the debugger for too long, or bad things will happen (the client loses connection, or more commonly, the web app mysteriously dies when you click the debug Resume command)
I don’t think these are new in 2022 R3, but I’m curious if others have seen them? We need to get these reported into the Issue tracker if not already…
Some objects seem particularly fond of crashing the app being debugged when viewing their properties in the variables inspector or whatever it’s called. Stepping code while viewing ListBox contents (especially tags) is very risky I think. Dictionaries too.
It took me a while to figure out something in a Web App. It may happen in a Desktop App also.
I was debugging a method by doing step by step execution, a breakpoint was set at the beginning. For about each line of the method I was having a look at the values for variables and object properties. Sometimes when I was stepping in that method, instead of going to the next line, the app was going to a previous line . How is that possible ???
Well, that method was called by a timer that was triggered every 10 minutes, but for debugging purposes I lowered the timer to two minutes. Since it took more than 2 minutes to do step by step and having a look at values, the timer continued and called the method again .
. How is that possible ???
.