| ??? 06/28/06 16:06 Read: times |
#119271 - the root Responding to: ???'s previous message |
hi,
Oliver Sedlacek said:
That seems to be the most common terminology on other processors. Indeed, here we call it "avost" by Russian term. But friends we forgot something. First of all, there are utilities which analyze source code, make tree of subroutines and calculate max. space size required. Indeed, as long as you do not use some hack tricks (= Another point is that if such failure occured even afrer the checking has been done with the above then it means not software failure but hardware one. And here we come to question of hardware stability. It is not a point "how to catch" it is the point to check a board desing, vendor errata(s) and other hardware-related things. Indeed, here I assume that this was not a lamer programmer mistake. I do not call me a master but for my 15-years experience with some processors and microcontrollers I have not "stack overflow" troubles yet except foolish programming typpos or hardware malfunctions. In any case: if such sh**t happened so you must not rely that any data including non-volatile one are correct as well as that you may determine states of your peripheral at the moment on it. By other words: it should not be software trap but full STOP and disabling of all hardware till operator check for it. This is because there is not warranty that your software trap is processsed good during hadrware failure (even red LED may not light on then, be sure! Regards, Oleg |
| Topic | Author | Date |
| best practice regarding SP | 01/01/70 00:00 | |
| an easier method | 01/01/70 00:00 | |
| the other way round | 01/01/70 00:00 | |
| as a general rule | 01/01/70 00:00 | |
| Good rule | 01/01/70 00:00 | |
| on stack and data | 01/01/70 00:00 | |
| Estimating stack usage | 01/01/70 00:00 | |
| The future is now | 01/01/70 00:00 | |
| I'd like it also as interrupt... | 01/01/70 00:00 | |
| where would you store the interrupt retu | 01/01/70 00:00 | |
| what return??? | 01/01/70 00:00 | |
| then don't call it an interrupt | 01/01/70 00:00 | |
| OK, call it... exception? | 01/01/70 00:00 | |
| Trap perhaps? | 01/01/70 00:00 | |
| trap! | 01/01/70 00:00 | |
| the root | 01/01/70 00:00 | |
| Fair point | 01/01/70 00:00 | |
| signaling | 01/01/70 00:00 | |
avost? | 01/01/70 00:00 |