As you have seen, different machine architectures do different things after
hitting a trap. On x86_64, the trap instruction is executed, and then you
stop, so the PC is left after the stop. On arm64, when execution halts the pc
is still pointing at the trap instruction.
I don't think lldb sho
Hi,
I'm noticing an unexpected difference between targets when I hit a dbgtrap in
the debugger. Consider this simple llvm function:
define void @do_break() {
entry:
call void @llvm.debugtrap()
ret void
}
If I compile that with llc and use lldb to launch a program that calls it, on
x
