default behavior for thread overrun

[daniel_dsouza]

Originally Posted by Ether

If I had a requirement or an expectation* that a task should never overrun, I'd add runtime code to monitor and report it. I'd leave this code in place for all in-house testing and practice, and probably for competition too.

I had wanted to try this for next year (we had some issues where our robot was hung up waiting for an input), but I didn't know how effectively I could have code monitor other code without things running in parallel. I'm no expert about our control system, but I thought that only one thread runs a time.