Re: [Valgrind-users] not stack'd, malloc'd or free'd, but written to anyway

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

On Mon, 29 Mar 2004, Xavier Bestel wrote:

> I've just tried 2.1.1 (with a slightly different version of my program)
> and I have exactely the same result. Although the address is different,
> the string dereferenced is the same, and valgrind keeps on pretending
> it's a virgin portion of memory.
> How can I easily help what looks like a valgrind bug ?

Please file a bug report (see valgrind.kde.org/bugs.html).  The more
relevant info you can include the better.

N