[PATCH v5 0/27] MR8026: Draft: RFC: Running wine with AddressSanitizer

[Yuxuan Shui (＠yshui)]

Please see: https://marc.info/?l=wine-devel&m=174715050805731 as well as the commit messages for more information.

--
  v5: ntdll: Report more info about heap problems detected by ASan.
      ntdll: Show (partial) stack trace in ASan reports.
      ntdll: Add heap quarantine for ASan.
      ntdll: Add asan poisoning and redzoning to heap allocator
      ntdll: Implement ASan fake stack.
      ntdll: Don't use address of local variables as the frame address.
      ntdll: During unwind, also check if frame is on fake stack.
      ntdll: Implement __asan_{un,}poison_memory_region.
      ntdll: Make sure to not write into poisoned memory in KeUserModeCallback.
      ntdll: Implement __asan_set_shadow_*.
      ntdll: Implement reporting of ASan errors.
      ntdll: Implement __asan_{memory,region}_is_poisoned.
      ntdll: Implement __asan_{un,}poison_stack_memory.
      ntdll: Unpoison stack in __asan_handle_no_return.
      ntdll: Add API for checking whether address is in fake stack frame.
      kernel32: Check for poison in LocalLock if ASan is enabled.
      kernel32: Fix ASan reports in IsBad*
      ntdll: Call __asan_handle_no_return in RtlRestoreContext.
      makedep: Support sanitizer flags.
      asan_dynamic_thunk: Add ASan dynamic thunk for DLLs.

This merge request has too many patches to be relayed via email.
Please visit the URL below to see the contents of the merge request.
https://gitlab.winehq.org/wine/wine/-/merge_requests/8026

[Jinoh Kang (＠iamahuman)]

On Thu May 15 20:34:14 2025 +0000, Alexandre Julliard wrote:
> I agree with Paul, getting the Windows runtime to work looks like a more
> promising solution. Sure, it would maybe test only 90% of the code, but
> that seems like a worthwhile trade-off for (presumably) much lower maintenance.

Some ASAN annotations can be shared with Valgrind, so maybe we can keep them; just make them nonspecific to ASAN.

For the rest, I'd generally vote for -fno-sanitize for 90% of the code. As we see more bug cases in support of ASAN, we can gradually and incrementally adopt the instrumentation.