14889cc06d
The Mach-O writer puts the unwinding records in a __unwind_info section, so just find the appropriate section and use its contents instead of forcing it to be at the end of the segment's memory space. Create an overload of UnwindingRecordsPlatform::RegisterExecutableMemory that takes a pointer to the start of the unwinding records for use by the Mach-O loader. Add __unwind_info for any executable segments that are not the text segment as well. Instead of testing host/target windows plus 64-bit arch, use the defines provided by platform/unwinding_records.h in the Mach-O writer and the ELF and Mach-O loaders. TEST=ci on Windows trybots Issue: https://github.com/dart-lang/sdk/issues/60307 Change-Id: Iee53c6725a681f44ac98ed9c9aecf1b75853ece5 Cq-Include-Trybots: luci.dart.try:vm-aot-linux-debug-x64-try,vm-mac-release-arm64-try,vm-aot-mac-release-arm64-try,vm-aot-mac-release-x64-try,vm-aot-dwarf-linux-product-x64-try,vm-linux-debug-x64-try,vm-mac-debug-arm64-try,vm-gcc-linux-try,vm-aot-win-release-arm64-try,vm-aot-win-release-x64-try,vm-win-release-x64-try,vm-win-release-arm64-try,vm-aot-win-debug-arm64-try,vm-win-debug-arm64-try Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/432960 Commit-Queue: Tess Strickland <sstrickl@google.com> Reviewed-by: Ryan Macnak <rmacnak@google.com> Reviewed-by: Slava Egorov <vegorov@google.com>