Displaying 2 results from an estimated 2 matches for "dbgtrap".
2020 Mar 04
2
Continuing from dbgtrap on different targets
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 x86_64 linux (Ubuntu 18.04), here's what I see at the stop:
Process 130404 sto...
2020 Mar 05
2
[lldb-dev] Continuing from dbgtrap on different targets
On 04/03/2020 21:45, Jim Ingham via llvm-dev wrote:
> 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 should be in the business of telling