| ??? 04/12/07 13:35 Read: times |
#137035 - a rare bug.... Responding to: ???'s previous message |
... is hard to find (provided your programming abilities won't jump in a second). If it happens once in... a hour, day, week, month, year... it's a problem to trace back - and is too easy to hide "coincidentally" (-> have no "proof" - or at least a good indication - that it was removed).
Thus, in these cases, the best thing to do is to try to increase the occurrence rate of the bug. If you suspect it is serial-related, push as many characters as possible (and, if possible, with irregular spaces). If you suspect it is timer related, try playing around with the timer reload value. Try to put as much changes from the external as possible - under pressure often the bugs crawl out. JW |
| Topic | Author | Date |
| two interrupts request at the same time | 01/01/70 00:00 | |
| datasheet | 01/01/70 00:00 | |
| right,but | 01/01/70 00:00 | |
| error? what kind of error? | 01/01/70 00:00 | |
| not reset,in debug PC don't change any more | 01/01/70 00:00 | |
| Sounds like an atomicity problem | 01/01/70 00:00 | |
| Maybe an event gets lost | 01/01/70 00:00 | |
| initialization sequencing | 01/01/70 00:00 | |
| a rare bug.... | 01/01/70 00:00 | |
Interupts | 01/01/70 00:00 |