Sillysoft Games

Does anybody have any debugging tips they'd like to share?

I'm currently using debug() to write in log.txt where the bot is running in the code and what certain variables are.

I used a window.

Create a JFrame add a text view etc. Maybe even a pause button. Call Show().

http://sillysoft.net/forums/viewtopic.p ... ight=frame

Real-time debugging is the best way to debug.

http://sillysoft.net/wiki/?real%20debugging

Bertrand wrote:Real-time debugging is the best way to debug.

http://sillysoft.net/wiki/?real%20debugging

QFT

Thanks guys, those are real time-savers!

Is there an easy way to see what the bot is doing besides manually stepping through the code via NetBeans?

I'm looking to fix a bug that occurs very infrequently, and I don't want to simply step through until it occurs.

I usually just let Lux automatically restart the game, and then come back in an hour or so to see if the bot has gotten itself into an endless loop.

When you're running the app inside the debugger, there should be a 'pause' button. So you can leave it running, and then 'pause' it once it's inside the infinite loop, and the debugger should show you where in the code it's stuck.

Or put code in to detect the loop and display a dialog, maybe beep to get your attention, them make use of the pause. That way the machine waits for the dialog doing nothing instead of running full tilt in some loop.

Thanks for the tips everybody!