default behavior for thread overrun

[Ether]

Originally Posted by Todd

I'm far from a VxWorks expert, but if the above is true, then from my experience if you wanted something like a task monitor in C++ that tracked task overrun and decided what to do when a task overran, you'd have to implement it yourself.

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.


* If there's an overrun where I completely expected there would never be one, I'd want to know it. It could point to a coding or design error, or even a fundamental misunderstanding of how the system works.