"Memory leakage" and variables being written into unintended locations are common causes of programming problems. A debugging technique that I developed years ago was to surround my variables with some "0" buffer space. Viewing the memory on a display, I could see when data started to intrude into the white "snow" and attack my programming bug. It sounds like the Micriµm µC/Probe would be a powerful tool to monitor memory and provide an alert when variables overwrite program space or other variables.
Sometimes, moving into the future drives you backwards. With many of the newer Microsoft Office applications, if you open a file directly, it is read-only and cannot be modified or saved. It is necessary to open Word / Excel first and then open the file. "Progress."
@ Doug, Max - Yeah, I know, I was surprised too, but that's the way he's always done it...
I still remember doing prelim PCB floorplans by cutting out post-it notes to the same size as ICs and circuit block estimates, them arranging them on a paper until I got all the interconnections as short as possible. Don't laugh - it got the job done :>}
I'd probably still use the OpenOffice draw program. It tracks yourmouse position and thus you can get quite accurate and repeatable drawings. I used it to design shelving in my house and to make room diagrams for placing furniture. You just ahd the translet thedistances on the drawing sinto physical distances but once I kniw the relationship, the rest was easy. It beat making paper mkodels of rooms and furniture, although that worked too.