Tracing a problem
BlitzMax Forums/BlitzMax Beginners Area/Tracing a problem
| ||
| I've got a rather nasty bug which I'm trying to trace at the moment which freezes my app. Aside from sprinkling debuglogs in every function to see what it last executed, is there a more elegant way of being able to track down where a program stopped executing (or got caught in an infinite loop etc)? Thanks |
| ||
| Rather than sprinkle debuglogs everywhere try adding a single debuglog to the start of a function... debuglog "Entered Function <name>" Recreate the problem a number of times and see if it's always the same function. Focus on that function. |
| ||
| I think thats the first time I've come across elegant and debug in the same breath... use SuperStrict gets about 80% of bugs! double check all your while loops have conditions that can be matched Are you modifying any for next loop counters Ideally the stop button would show you in the code window where you interupted it...(maybe in the future) |
| ||
| I've had major problems with superstrict. Every third or fourth time I run the program I get the 'program too big to fit into memory' error that sometimes happens. It may just be coincidence, but its a mighty big one if it is. Thanks for the help guys |
   |