|
From: Jeremy F. <je...@go...> - 2003-11-03 17:04:17
|
On Mon, 2003-11-03 at 07:21, arn...@re... wrote:
> I complied it with gcc and ran valgrind --skin=memcheck
> --leak-check=yes --leak-resolution=high --show-reachable=yes
> test_leak.
>
> Valgrind did detect all problems but did not detect the strcpy errors
> (stack overwrite) on variables str2 and str3.
>
> Looks like a valgrind bug to me.
That's definitely an error we'd like to catch, but we can't at present.
The problem is that there's no way from looking at the machine-code
itself to tell what the bounds of the arrays on stack are, so we can't
check accesses to them. Nick is hoping to be able to extract enough
details from the debug information so we can use that to determine the
bounds of arrays on the stack.
So, it isn't a bug in the sense that Valgrind is supposed to check for
it now, but it is something we'd like to have.
J
|