| ??? 06/16/06 12:24 Read: times |
#118405 - nuclear explosions Responding to: ???'s previous message |
The link that Charles references conveniently ignores atomicity issues
I believe ignoring atomicity is the most common reason for "it works just fine but..." It seems a lot of the published code I see seems to ignore atomicity issues - obviously it isn't well known but the effects can be random and hard to track down. They are dead easy to "track down". The only thing that makes the difficult is the approach (debugging). It should be MANDATORY whether there is a problem or not that for every project each and every variable that is used both outside and inside an ISR be given a full "desk analysis". For a huge program that process takes about an hour. Erik |
| Topic | Author | Date |
| Timer0_ISR delay troubles | 01/01/70 00:00 | |
| Why it doesn't work | 01/01/70 00:00 | |
| Extra Atomic | 01/01/70 00:00 | |
| Been there Done That | 01/01/70 00:00 | |
| Yes,very atomic | 01/01/70 00:00 | |
| nuclear explosions | 01/01/70 00:00 | |
| Also | 01/01/70 00:00 | |
| Thanks everyone | 01/01/70 00:00 | |
| learn to swim before diving in | 01/01/70 00:00 | |
| using 1 | 01/01/70 00:00 | |
| Some code from the prof broke interrupt | 01/01/70 00:00 | |
| Nevermind | 01/01/70 00:00 | |
| which it is not | 01/01/70 00:00 | |
Explain? | 01/01/70 00:00 | |
| What happend to common sense? | 01/01/70 00:00 | |
| specific examples are dangerous | 01/01/70 00:00 | |
| Uncommon Sense | 01/01/70 00:00 | |
| Practical programming | 01/01/70 00:00 | |
| Charles | 01/01/70 00:00 |