Tracing a problem

BlitzMax Forums/BlitzMax Beginners Area/Tracing a problem

The forum is locked. These are the original blitzbasic.com forums, kept so they can still be read. No new topics, replies or edits can be made here. To join in, head over to the Blitz3D+ forums.

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