runtime: fix compile failure from use of _Unwind_Backtrace() on FreeBSD 13.0 #61693
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FreeBSD's libunwind situation is complex. It uses LLVM's libunwind library, built as part of FreeBSD's libgcc_s.so. (The latter, despite its name, does not actually come from gcc in modern FreeBSD.)
However, it also uses libcxxrt (not LLVM's libcxxabi). libcxxrt installs an <unwind.h> originally from https://github.com/libunwind/libunwind. That <unwind.h> surrounds its declaration of _Unwind_Backtrace with _GNU_SOURCE guards.
Therefore: on FreeBSD, define _GNU_SOURCE so that withCurrentBacktraceImpl() can access _Unwind_Backtrace.
For posterity, a (probably partial) list of the various <unwind.h>s (and how they relate to this change):