Message406739
Reproducible on 3.9, 3.10, and on main.
The --with-memory-sanitizer option adds "-fsanitize=memory -fsanitize-memory-track-origins=2 -fno-omit-frame-pointer" to CFLAGS, and "-fsanitize=memory -fsanitize-memory-track-origins=2" to LDFLAGS. The MemorySanitizer is a clang specific feature, AFAIK. You're using GCC, so what happens is that these (GCC incompatible) flags are added and the following compile check (getaddrinfo) fails.
IMO, adding a compiler check and printing a warning if --with-memory-sanitizer is used with GCC should be an ok solution. Alternatively, we inform the user that we're switching to using the leak sanitiser, if we're on GCC.
+pablo
See also:
- https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html
- https://clang.llvm.org/docs/MemorySanitizer.html |
|
Date |
User |
Action |
Args |
2021-11-21 21:33:58 | erlendaasland | set | recipients:
+ erlendaasland, JaonHax |
2021-11-21 21:33:58 | erlendaasland | set | messageid: <1637530438.43.0.0682533712152.issue42268@roundup.psfhosted.org> |
2021-11-21 21:33:58 | erlendaasland | link | issue42268 messages |
2021-11-21 21:33:58 | erlendaasland | create | |
|