On targets with a return address register (e.g. $lr on arm), when the unwinder is asked to fetch the caller's pc, we rewrite that to fetch the return address value.
However, when we're in a trap handler -- either from an interrupt or an async signal -- we will have a full register context for the frame that was interrupted/trapped. The unwinder correctly allows you to fetch volatile registers when you're above a trap handler. But we are still rewriting the "fetch the pc" request when the trap handler is asked to find the caller's saved pc. This is incorrect, and results in lldb showing the wrong function that was interrupted/faulted.