??? 06/28/06 18:29 Modified: 06/28/06 18:54 Read: times |
#119278 - signaling Responding to: ???'s previous message |
hi,
Oliver Sedlacek said:
You're probably not going to want to do much after a stack overflow trap except to signal that the trap occured and then stop. Indeed, but due nature of the hardware malfunction you cannot be sure that "error signal" (LED, beeper etc) will be delivered always. Many years ago when programs were always placed into external ROM I heard that there were hardware checkers for this problem. But once again: if software is made with mistakes then it may help. But if there is hardware problem then you cannot be sure. Even hardware detector may do false hit itself! (= As about "nested interrupts" - yes, they do it and even take care about possible stack increase due priority of them I cannot remember where I have read on this, maybe Keil or Silabs forums, sorry. Once again: the problem is like a myth for me. If I realy doubt about this so I have switch to appropriate derivative or pass work to other programmer under other featured core. I`ll never experiment with mass-production: only checked and verifyed blocks are used then. Of course I do elaboration with new ideas but not for the question of topic. Hardcoding is good but dangerous hobby (= Read http://www.8052.com/forum/read.phtml?id=98860 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 |