When debugging Android 64-bit (ARM64) applications, hovering over a floating point instruction causes a popup to appear with the message:
“Bad register number passed to arm.get_register_value: 163”.
This error appears to originate from the GDB backend. However, any attempt to dismiss the message—or to disable it via the “Don’t display this message” checkbox—results in the popup reappearing continuously. This creates an endless UI loop that prevents further progress in the debugging session.
Hello @Uncle ,
Thanks for reporting this! We’re investigating whether this is a common issue and will keep you posted as we gather more information.
Hello @Uncle,
I’m returning with an update - we’ve reproduced the issue, and it appears to be an annoying bug. We’ve added this to our bug list, and it shouldn’t take too long to fix—stay tuned!
Same problem occurs when clicking/hovering over the zero register in the arm, e.g. XZR, which results in the 160 error. I haven’t checked other registers. This bug may affect other registers as well.
Hello again @Uncle,
Great news — the bug has already been fixed! You can expect the fix in the next IDA release, which is coming out soon!
Hi @failed_state, — just a quick update to let you know that the XZR/zero register has also been addressed.
