You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My junior classmate is trying to learn C++ with my vscode tutorial that uses clang installed by msys2 on windows, but I noticed project_options won't enable sanitizers for him because,
No sanitizer is supported for the current platform/compiler
I removed the above NOT "${CMAKE_SYSTEM_NAME}" STREQUAL "Windows" and configured again, the sanitizers are enabled and work correctly.
So I'm wondering why dose project_options disable clang/gcc sanitizers on windows and I suggest maybe we should investigate the current support for sanitizers on windows. (BTW Unfortunately, I can't reach my windows computer until next year).
Upvote & Fund
@aminya is using Polar.sh so you can upvote and help fund this issue. The funding is received once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog!
The text was updated successfully, but these errors were encountered:
My junior classmate is trying to learn C++ with my vscode tutorial that uses clang installed by msys2 on windows, but I noticed project_options won't enable sanitizers for him because,
project_options/src/Sanitizers.cmake
Lines 172 to 174 in 86e68a9
As a result, the cmake configuration says,
I removed the above
NOT "${CMAKE_SYSTEM_NAME}" STREQUAL "Windows"
and configured again, the sanitizers are enabled and work correctly.So I'm wondering why dose project_options disable clang/gcc sanitizers on windows and I suggest maybe we should investigate the current support for sanitizers on windows. (BTW Unfortunately, I can't reach my windows computer until next year).
Upvote & Fund
@aminya is using Polar.sh so you can upvote and help fund this issue. The funding is received once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog!
The text was updated successfully, but these errors were encountered: