Re:Force an interrupt by software
It's very critical for test and debug to get code to execute all paths and make sure that the expected things happen. Any code path that hasn't been tested should be assumed to not work.
Calling a routine that is called when a specific interrupt condition occurs is not the same as testing and verifying that your interrupt handler will work, call the necessary routine(s), clean up after itself, et cetera if that condition should occur. The only way to be absolutely sure is to have the code actually have to handle the interrupt, not just pretend that the interrupt happened.
login or register to reply
|