https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234201
--- Comment #7 from Dimitry Andric <d...@freebsd.org> --- (In reply to Dave Baukus from comment #6) > We are seeing this same issue on Release-12.0 in a large Java application; > one of our Java developers created a small, standalone test that emits the > libunwind error message and core dumps If it is possible, it would be nice to attach the jar. > The problem does NOT occur on FreeBSD-12.0-STABLE-amd64-20190517-r347885. Is > anyone aware of a specific fix ? 12.0-RELEASE shipped with clang 6.0.1 and a fairly old version of llvm-libunwind. While I updated llvm and clang a few times, I didn't handle llvm-libunwind until the 8.0.0 import in base r346168. There, I upgraded llvm-libunwind to the same upstream revision as the rest of llvm and clang, e.g. upstream 8.0.0 final r356365. Unfortunately that is rather a huge commit, also for the libunwind part, so it is not easy to pinpoint one exact upstream revision that fixes this particular issue. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
