https://github.com/google/sanitizers/issues/1716#issuecomment-2010399341
Summarizing: newer ThreadSanitizer has been updated to be able to work with vm.mmap_rnd_bits = 30, but not higher than that. For other cases, it will now re-execute the binary with ASLR disabled, if possible. For most people the quick workaround of setting vm.mmap_rnd_bits to 28 might work, but of course you won't get the benefits intended with #1983357 either. So at some point, it would be nice to have the upstream ThreadSanitizer fixes backported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056762 Title: ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
