Interrupt triggered bugs are usually really hard to find Very true. Anything that is reproducible is fairly easy to debug. Something that is hard to reproduce

Interrupt triggered bugs are usually really hard to find Very true. Anything that is reproducible is fairly easy to debug. Something that is hard to reproduce is even harder to figure out. Here's a good scenario, on a good old Apple II: you'd call a subroutine. The processor would put your address on the stack, to know where to return. So when the processor returns, you can peek at the data just below the stack pointer to figure out your own address. Works 99.999999% of the time. Except if an interrupt occured exactly on the return instruction, erasing the old stack data. With that kind of frequency (interrupts would happen at about 60 Hz on an Apple II), you'd freeze the computer after several minutes. Good luck figuring it out.