Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
04/29/02 14:06
Read: times


 
#22266 - RE: Sleeping Bugs in the code:
A couple of things to add:

A phrase of mine referring to the method described by Craig: " I do not code a project, I grow it"

Keep ISRs short (and sweet)

Any unused interrupt can be used as a low priority "software interrupt" which can take "the long" out of a hardware interrupt.

Have a routine void Crash(void); set a breakpoint there and whenever it is called find the callers address in the stack.
Uses of Crash():
At default:
If a function will only work if a variable is less than 10 (e.g. array offset), then insert: if (var > 9) Crash();

Play it safe, have fun,

Erik





List of 17 messages in thread
TopicAuthorDate
Sleeping Bugs in the code:            01/01/70 00:00      
RE: Sleeping Bugs in the code:            01/01/70 00:00      
RE: Sleeping Bugs in the code:            01/01/70 00:00      
RE: Sleeping Bugs in the code:            01/01/70 00:00      
RE: Sleeping Bugs in the code:            01/01/70 00:00      
RE: Sleeping Bugs in the code:            01/01/70 00:00      
RE: Sleeping Bugs in the code:            01/01/70 00:00      
RE: Sleeping Bugs in the code:            01/01/70 00:00      
RE: Sleeping Bugs in the code: - more            01/01/70 00:00      
RE: Sleeping Bugs in the code: - more            01/01/70 00:00      
RE: Sleeping Bugs in the code: - more            01/01/70 00:00      
RE: Sleeping Bugs in the code: - more            01/01/70 00:00      
RE: Sleeping Bugs in the code:            01/01/70 00:00      
RE: Sleeping Bugs in the code:            01/01/70 00:00      
RE: crash()            01/01/70 00:00      
RE: crash()            01/01/70 00:00      
RE: Sleeping Bugs in the code:            01/01/70 00:00      

Back to Subject List