This is the mail archive of the
mailing list for the GCC project.
Re: ACATS tests that fail valgrind check
On 2005-01-12, Duncan Sands <firstname.lastname@example.org> wrote:
> (6) "Address ... after a block ... alloc'd"
> Seems to mean that part of a new block of allocated memory was already
This valgrind error usually means you've run off the end of a malloc()-ed
block of memory. IIRC you get told where the bad read/write happens and
also where the block nearest to that location was allocated.