This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] New -fstack-check implementation
> in the past valgrind has noticed invalid memory accesses when using
> -fstack-check in a multi-tasking program for example when a task exits
> (the invalid accesses coming from the stack checking code). Is this a
> known (fixed) problem? If not, I will try to cook up a testcase.
By definition, stack checking using any probing mechanism will generate
"invalid" accesses.