| ??? 12/12/02 01:46 Read: times |
#34294 - RE: How to use software traps? Michael |
<html>
I disagree with Michael. Suppose programmer A has executed his project as Michael specifies. Programmer B has done the same, but has taken the additional step of filtering his hex file so that all unused areas of PROM are covered by traps as discussed in this thread. Who has produced the more reliable product? You can prove that a simple program is free of bugs, but once it gets moderately complex, the possibilities for errors increase proportionally (or maybe exponentially ...). And no guaranteeing that ALL the bugs are out. I have used this method to trap errors in both software and hardware (and to prove to the hardware engineers that an error was NOT in software :) ...). A watchdog timer is fine and good, but will not catch events where a thread (any thread) is recovered in time to prevent the watchdog from triggering. In the meantime, the code that was executed was not the code intended by the designers, and luck determines how bad the result of executing this unintended code is. On a side note, you should also add these traps to protect areas of constants from being executed, not just functions. <table><tr><td>james</td><td> </td><td> www.jameshinnant.com</td></tr></table> </html> |
