Open bhaible opened 3 months ago
Thanks. I think the non-DWARF5 failures are fixed now. On the machine I tested on, on the GCC compile farm, the DWARF5 failures appear to be due to bugs in the dsymutil program, which doesn't seem to understand DWARF5 yet. However, I don't know how to find out which version of macOS that machine is running. dsymutil -v reports
Apple LLVM version 14.0.0 (clang-1400.0.29.202)
Optimized build.
Default target: arm64-apple-darwin21.6.0
Host CPU: apple-a12
Can you update to libbacktrace HEAD and see what testsuite failures you get now? Thanks.
With current libbacktrace HEAD:
Configuring with libbacktrace_cv_lib_dwarf5=no ./configure
, there are no test failures any more.
Configuring with the default ./configure
, there are 2 test failures:
FAIL: dwarf5
FAIL: dwarf5_alloc
Here is the log from "make check": make_check.log.gz
Btw, the macOS version of that machine is
$ sw_vers
ProductName: macOS
ProductVersion: 12.6
BuildVersion: 21G115
(My statement that it was macOS 12.5 was incorrect. There is not a 1:1 mapping between Darwin versions and macOS versions. See https://en.wikipedia.org/wiki/MacOS_Monterey#Release_history )
Hopefully Apple will fix dsymutil to support DWARF 5.
On a macOS 12.5 machine, building libbacktrace (current git HEAD) and running "make check" produces 7 test failures:
Here is the test-suite.log: test-suite.log.gz
It seems that the compiler and tooling don't support dwarf 5 well. When configured with
libbacktrace_cv_lib_dwarf5=no ./configure
, there are only 5 test failures:To reproduce, you can use the
cfarm104
machine of the GCC compile farm https://portal.cfarm.net/ . Alternatively, macOS 12 machines are also available through GitHub actions.