Can I ask someone to clarify what we mean by "sort the debugger out". It's a bit woolly - what is it that we want it to be able to do?
Run for a few moments without crashing, taking Blide and my application with it. Whenever I start opening up the debug tree to find all the fields of a particular object, perhaps nested inside another object, there's a 1 in 3 chance that the debugger will just promptly freeze and take everything else with it. And I know it's not Blide because it does it in the official IDE too, when I can bear to use it.
In terms of what abilities I'd like it to have, well it would be nice to be able to stop the program, change some values and set it off again, but I'd really settle for it just not tripping over itself every five minutes.