Re: [Valgrind-users] My first test with Valgrind (it missed some points)...

[Brad H. <br...@fr...>]

On Sunday 28 October 2007 09:33:12 am Danett song wrote:
> 3)A stack overflow using strcpy() at Line 24 -
> strcpy(destino, argv[1]);
That necessarily isn't an error. If argv[1] can fit into destino, then there 
is no bug. Valgrind can't tell you about an error that might occur with 
different input.

Possibly a static analysis tool can warn you that strcpy is a bad idea. In 
this case, something like flawfinder is probably about the right level. See: 
http://www.dwheeler.com/flawfinder/

> 4) A off by 1 using a loop to fill the array at line
> 28-32.
I don't know about this one.
As a guess, this might not be showing up on your architecture because the 
array doesn't have anything after it. Try re-ordering the variable 
declaration or adding something at the end.

Brad