https://github.com/al13n321 updated
https://github.com/llvm/llvm-project/pull/103473
>From 3beb6fc40ccc0b5726b360156063ef35e2b1db3f Mon Sep 17 00:00:00 2001
From: Michael Kolupaev
Date: Tue, 13 Aug 2024 21:16:08 +
Subject: [PATCH] [libunwind][X86-64] Handle Linux sigreturn trampoline when
al13n321 wrote:
Feel free to close this PR if such change is not going to be accepted.
https://github.com/llvm/llvm-project/pull/103476
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
al13n321 wrote:
The `clone` syscall, in newly created thread, adjusts stack pointer and stack
contents, and there's logically no "caller" stack frame and no return address
on the stack. `tools/add-cfi.x86_64.awk` doesn't know about any of that and
autogenerates cfi as if it's just normal linea
https://github.com/al13n321 created
https://github.com/llvm/llvm-project/pull/103476
If an unwind step leaves both the instruction pointer and the stack pointer
unchanged, stop unwinding. Otherwise we'd be stuck in a loop producing the same
stack frame over and over.
This happens with musl li
https://github.com/al13n321 created
https://github.com/llvm/llvm-project/pull/103473
Do for X86-64 what libunwind already does for AArch64, RISC-V, and S390X. GDB
does this too.
Useful for musl libc, which doesn't have DWARF unwind info for `__restore_rt`
trampoline, so libunwind couldn't unw
