Re: [Valgrind-users] suppress warning repetition

[Tom H. <to...@co...>]

On 02/01/15 00:44, "João M. S. Silva" wrote:

> Is there a way to check for stack memory errors? If it was not for the
> %s in the command string it could be caught with cppcheck, but with the
> %s only a runtime check would do, I guess.

Try building with -fsanitize=address which is a clang/gcc tool that does 
similar things to valgrind, but because it works at compile time it can 
insert gaps between stack variables.

Tom

-- 
Tom Hughes (to...@co...)
http://compton.nu/