Re: [Valgrind-developers] New implementations of strncpy() and strncat() broken?

[Nicholas N. <nj...@ca...>]

On Fri, 25 Apr 2003, Adam Gundy wrote:

> The new memcheck provided versions of strncpy() and strncat() will
> read one byte past the maximum number 'n' bytes in 'src'. If this byte is not
> initialised, you get a spurious error report from valgrind.
>
> I can't _actually_ find a spec anywhere which says what is supposed to
> happen if the source string is not nul terminated, but I'm pretty sure it's a
> bug.

Ah, good catch.  I knew I wouldn't be able to write them bug-free.  Lucky
Valgrind can check at least some parts of itself :)

I will commit, thanks.

N