memcheck/tests/amd64-linux/reallocarray.stderr.exp - master - niceSOFT/valgrind

memcheck/tests/amd64-linux/reallocarray.stderr.exp

64 строки3 KB

Paul Floyd

Bug 515731 - Distinguish between realloc functions in realloc size 0 error messages

12 фев 2026, 09:45

12 фев 2026, 09:458b2fbed


All heap blocks were freed -- no leaks are possible

Added leak check, expect 40 bytes still reachable
LEAK SUMMARY:
   definitely lost: 0 (+0) bytes in 0 (+0) blocks
   indirectly lost: 0 (+0) bytes in 0 (+0) blocks
     possibly lost: 0 (+0) bytes in 0 (+0) blocks
   still reachable: 40 (+40) bytes in 1 (+1) blocks
        suppressed: 0 (+0) bytes in 0 (+0) blocks
Reachable blocks (those to which a pointer was found) are not shown.
To see them, rerun with: --leak-check=full --show-leak-kinds=all

reallocarray() with size 0
   at 0x........: reallocarray (vg_replace_malloc.c:...)
   by 0x........: main (reallocarray.c:19)
 Address 0x........ is 0 bytes inside a block of size 40 alloc'd
   at 0x........: reallocarray (vg_replace_malloc.c:...)
   by 0x........: main (reallocarray.c:14)

Added leak check, expect all blocks freed
All heap blocks were freed -- no leaks are possible

reallocarray() with size 0
   at 0x........: reallocarray (vg_replace_malloc.c:...)
   by 0x........: main (reallocarray.c:25)
 Address 0x........ is 0 bytes inside a block of size 10 alloc'd
   at 0x........: malloc (vg_replace_malloc.c:...)
   by 0x........: main (reallocarray.c:23)

Added leak check, expect all blocks freed
All heap blocks were freed -- no leaks are possible

Added leak check, expect 40 bytes still reachable
LEAK SUMMARY:
   definitely lost: 0 (+0) bytes in 0 (+0) blocks
   indirectly lost: 0 (+0) bytes in 0 (+0) blocks
     possibly lost: 0 (+0) bytes in 0 (+0) blocks
   still reachable: 40 (+0) bytes in 1 (+0) blocks
        suppressed: 0 (+0) bytes in 0 (+0) blocks
Reachable blocks (those to which a pointer was found) are not shown.
To see them, rerun with: --leak-check=full --show-leak-kinds=all

Added leak check, expect 40 bytes still reachable
LEAK SUMMARY:
   definitely lost: 0 (+0) bytes in 0 (+0) blocks
   indirectly lost: 0 (+0) bytes in 0 (+0) blocks
     possibly lost: 0 (+0) bytes in 0 (+0) blocks
   still reachable: 40 (+0) bytes in 1 (+0) blocks
        suppressed: 0 (+0) bytes in 0 (+0) blocks
Reachable blocks (those to which a pointer was found) are not shown.
To see them, rerun with: --leak-check=full --show-leak-kinds=all

Added leak check, expect all blocks freed
All heap blocks were freed -- no leaks are possible


HEAP SUMMARY:
    in use at exit: 0 bytes in 0 blocks
  total heap usage: 4 allocs, 4 frees, 562,949,953,421,402 bytes allocated

For a detailed leak analysis, rerun with: --leak-check=full

For lists of detected and suppressed errors, rerun with: -s
ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)