On Wed Jan 24 18:20:38 2024 +0000, Jinoh Kang wrote:
Can we still support macOS libraries? Some sources claim that [DWARF unwinding information may be unavailable for functions that have unwinding information encoded in Apple compact unwinding format](https://faultlore.com/blah/compact-unwinding/):
Clang also started preferentially emitting that format over DWARF CFI
on Apple’s platforms. So to generate good backtraces on Apple platforms, you need to be able to parse and interpret compact unwinding tables.
Thanks; that’s probably quite true - in that case we probably shouldn’t get rid of libunwind here, until we have a complete enough unwinder for the compact unwinding format - or until we have better knowledge on the situation (e.g. if we could conclude with some certainty that we don’t need to unwind through functions with such data - or if we could disable the compact unwinding format for the unixlibs; the amount of non-PE code that the unwinder needs to handle is pretty small these days).