Yes all “normal” ISAs including 8080 and x86 guarantee that instructions are atomic with respect to interrupts on the same core. Either an instruction has fully executed and all its architectural effects are visible (in the interrupt handler), or none of them are. Any deviations from this rule are generally carefully documented. For example, Intel’s … Read more
You should generally NOT ignore the exception. Take a look at the following paper: Don’t swallow interrupts Sometimes throwing InterruptedException is not an option, such as when a task defined by Runnable calls an interruptible method. In this case, you can’t rethrow InterruptedException, but you also do not want to do nothing. When a blocking … Read more
The alternative to calling stop is to use interrupt to signal to the thread that you want it to finish what it’s doing. (This assumes the thread you want to stop is well-behaved, if it ignores InterruptedExceptions by eating them immediately after they are thrown and doesn’t check the interrupted status then you are back … Read more
What is the difference between the following ways of handling InterruptedException? What is the best way to do it? You’ve probably come to ask this question because you’ve called a method that throws InterruptedException. First of all, you should see throws InterruptedException for what it is: A part of the method signature and a possible … Read more