This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ACATS tests that fail valgrind check

On 2005-01-12, Duncan Sands <duncan.sands@math.u-psud.fr> wrote:
> (6) "Address ... after a block ... alloc'd"
> Seems to mean that part of a new block of allocated memory was already
> allocated.

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.

Cheers,
    Olly
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]