Of course we have all experinced a CPU that has gone off to execute garbage. This does happen when developing code, one too many pushes or pop's is often the cause, or perhaps an N-Way branch that has gone N+1 ways... heheh.
My question is, Once a product is fully debugged and you've covered all
the push/pop's etc... What is the need to trap CPU run away, and have you ever experienced it happening?


PS. When a CPU runs away, it's many legs makes it hard to catch! ;)