LINUX.ORG.RU

История изменений

Исправление Deleted, (текущая версия) :

Ничего особенного:

$ valgrind valgrind
==12153== Memcheck, a memory error detector
==12153== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==12153== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==12153== Command: /usr/bin/valgrind
==12153== 
==12153== Warning: invalid file descriptor -1 in syscall close()
==12156== 
==12156== HEAP SUMMARY:
==12156==     in use at exit: 10,472 bytes in 55 blocks
==12156==   total heap usage: 63 allocs, 8 frees, 13,656 bytes allocated
==12156== 
==12156== LEAK SUMMARY:
==12156==    definitely lost: 0 bytes in 0 blocks
==12156==    indirectly lost: 0 bytes in 0 blocks
==12156==      possibly lost: 0 bytes in 0 blocks
==12156==    still reachable: 10,472 bytes in 55 blocks
==12156==         suppressed: 0 bytes in 0 blocks
==12156== Rerun with --leak-check=full to see details of leaked memory
==12156== 
==12156== For counts of detected and suppressed errors, rerun with: -v
==12156== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)
valgrind: no program specified
valgrind: Use --help for more information.
Работает и valgrind valgrind valgrind и далее (пробовал до шести уровней). В valgrind, по его утверждениям, утечек памяти, да и вообще ошибок работы с памятью нет.

Исходная версия Deleted, :

Ничего особенного:

$ valgrind valgrind
==12142== Memcheck, a memory error detector
==12142== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==12142== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==12142== Command: /usr/bin/valgrind
==12142== 
==12142== Warning: invalid file descriptor -1 in syscall close()
==12145== 
==12145== HEAP SUMMARY:
==12145==     in use at exit: 10,472 bytes in 55 blocks
==12145==   total heap usage: 63 allocs, 8 frees, 13,656 bytes allocated
==12145== 
==12145== LEAK SUMMARY:
==12145==    definitely lost: 0 bytes in 0 blocks
==12145==    indirectly lost: 0 bytes in 0 blocks
==12145==      possibly lost: 0 bytes in 0 blocks
==12145==    still reachable: 10,472 bytes in 55 blocks
==12145==         suppressed: 0 bytes in 0 blocks
==12145== Rerun with --leak-check=full to see details of leaked memory
==12145== 
==12145== For counts of detected and suppressed errors, rerun with: -v
==12145== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)
valgrind: no program specified
valgrind: Use --help for more information.
roman@franchuk-r:~$ valgrind valgrind
==12153== Memcheck, a memory error detector
==12153== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==12153== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==12153== Command: /usr/bin/valgrind
==12153== 
==12153== Warning: invalid file descriptor -1 in syscall close()
==12156== 
==12156== HEAP SUMMARY:
==12156==     in use at exit: 10,472 bytes in 55 blocks
==12156==   total heap usage: 63 allocs, 8 frees, 13,656 bytes allocated
==12156== 
==12156== LEAK SUMMARY:
==12156==    definitely lost: 0 bytes in 0 blocks
==12156==    indirectly lost: 0 bytes in 0 blocks
==12156==      possibly lost: 0 bytes in 0 blocks
==12156==    still reachable: 10,472 bytes in 55 blocks
==12156==         suppressed: 0 bytes in 0 blocks
==12156== Rerun with --leak-check=full to see details of leaked memory
==12156== 
==12156== For counts of detected and suppressed errors, rerun with: -v
==12156== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)
valgrind: no program specified
valgrind: Use --help for more information.
Работает и valgrind valgrind valgrind и далее (пробовал до шести уровней). В valgrind, по его утверждениям, утечек памяти, да и вообще ошибок работы с памятью нет.