ACATS tests that fail valgrind check

[Duncan Sands]

On Thursday 13 January 2005 00:22, Olly Betts wrote:
> 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.

Hi Olly, you are right.  I read it wrong: my script picked it up as a new error, but in
fact it was additional information about an invalid read:

==3253== Invalid read of size 1
==3253==    at 0x80523DB: interfaces__cobol__valid_numeric (i-cobol.adb:646)
==3253==    by 0x805C9BD: cxb4003__test_block__display_format__valid.418 (i-cobol.adb:1008)
==3253==    by 0x805E3C1: _ada_cxb4003 (cxb4003.adb:226)
==3253==    by 0x8049E08: main (b~cxb4003.adb:152)
==3253==  Address 0x1BA4F678 is 0 bytes after a block of size 8 alloc'd
==3253==    at 0x1B9055B4: malloc (vg_replace_malloc.c:130)
==3253==    by 0x804F2ED: __gnat_malloc (s-memory.adb:92)
==3253==    by 0x805D041: _ada_cxb4003 (cxb4003.adb:116)
==3253==    by 0x8049E08: main (b~cxb4003.adb:152)

All the best,

Duncan.