https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63489
--- Comment #4 from Jonathan Wakely ---
I think valgrind only checks heap memory, so doesn't help for buffer overflows
on the stack.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63489
--- Comment #3 from Jonathan Hogg ---
Confirmed, this is the cause is the larger example as well. I had missed the
introduction of -fsanitize=address, useful feature. I'd assumed something like
that valgrind would have picked up for me however!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63489
--- Comment #2 from Jonathan Wakely ---
That was pretty easily found with -fsanitize=address
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63489
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
