I bisected, and it seems to have regressed with https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=f732bf6a603721f61102a08ad2d023c7c2670870 ["libsanitizer: merge from upstream (0a1bcab9f3bf75c4c5d3e53bafb3eeb80320af46].
Unfortunately, that is a fairly large merge from the upstream sanitizer libraries, so it is not that easy to pinpoint where the culprit is. I tried very recent gcc master, and there the test with -fsanitize=address -fstack-protector even segfaults! So I guess an upstream gcc bug report is probably the best way forward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023424 Title: GCC 13 on Lunar exhibits AddressSanitizer/UndefinedBehaviorSanitizer bug that doesn't manifest elsewhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-13/+bug/2023424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
