[Bug sanitizer/80953] Support libsanitizer on Solaris
ebotcazou at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Mon Feb 11 09:52:00 GMT 2019
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80953
--- Comment #33 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> I found that enabling it causes quite a number of regressions. Here's
> the list that I've just recreated:
>
> +FAIL: c-c++-common/asan/heap-overflow-1.c -O0 output pattern test
> +FAIL: c-c++-common/asan/heap-overflow-1.c -O1 output pattern test
> +FAIL: c-c++-common/asan/heap-overflow-1.c -O2 output pattern test
> +FAIL: c-c++-common/asan/heap-overflow-1.c -O2 -flto output pattern test
> +FAIL: c-c++-common/asan/heap-overflow-1.c -O2 -flto -flto-partition=none
> output pattern test
> +FAIL: c-c++-common/asan/heap-overflow-1.c -O3 -g output pattern test
> +FAIL: c-c++-common/asan/heap-overflow-1.c -Os output pattern test
>
> +FAIL: c-c++-common/asan/pr70541.c -O0 output pattern test
>
> +FAIL: c-c++-common/asan/strncpy-overflow-1.c -O0 output pattern test
> +FAIL: c-c++-common/asan/strncpy-overflow-1.c -O1 output pattern test
> +FAIL: c-c++-common/asan/strncpy-overflow-1.c -O2 output pattern test
> +FAIL: c-c++-common/asan/strncpy-overflow-1.c -O2 -flto output pattern
> test
> +FAIL: c-c++-common/asan/strncpy-overflow-1.c -O2 -flto
> -flto-partition=none output pattern test
> +FAIL: c-c++-common/asan/strncpy-overflow-1.c -O3 -g output pattern test
> +FAIL: c-c++-common/asan/strncpy-overflow-1.c -Os output pattern test
> +FAIL: c-c++-common/asan/use-after-free-1.c -O0 output pattern test
> +FAIL: c-c++-common/asan/use-after-free-1.c -O1 output pattern test
> +FAIL: c-c++-common/asan/use-after-free-1.c -O2 output pattern test
> +FAIL: c-c++-common/asan/use-after-free-1.c -O2 -flto output pattern test
> +FAIL: c-c++-common/asan/use-after-free-1.c -O2 -flto -flto-partition=none
> output pattern test
> +FAIL: c-c++-common/asan/use-after-free-1.c -O3 -g output pattern test
> +FAIL: c-c++-common/asan/use-after-free-1.c -Os output pattern test
> +FAIL: g++.dg/asan/deep-stack-uaf-1.C -O0 output pattern test
>
> Maybe this goes away with your unwinding fix, though.
OK, that was a second unwinding issue, now fixed too.
Can you remind me of the issue in 64-bit mode? Inconvenient memory layout,
right? It seems to be present on Linux as well.
More information about the Gcc-bugs
mailing list