Alternatively SANITIZER_LIMIT_FRAME_SIZE could be disabled altogether when building for windows.
I prefer the relatively localized disabling of the warning with the #pragmas as you've done as opposed to building the sanitizer builds with different settings.
I'm concerned about what looks to be an existing possible buffer overrun.
LGTM, but please take the suggested edit to update a documentation URL.
URL update in case the redirect goes bad in the future.
Unlike other Win32 APIs, the "wide" versions seem to be enabled by DBGHELP_TRANSLATE_TCHAR rather than UNICODE. LLVM doesn't seem to use that, so I guess this works for now. Using sizeof(TCHAR) now might ease a future transition, but I'll leave it up to you.