Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lst_insert_before #5

Open
mymedia2 opened this issue Apr 25, 2015 · 0 comments
Open

lst_insert_before #5

mymedia2 opened this issue Apr 25, 2015 · 0 comments
Labels

Comments

@mymedia2
Copy link
Owner

valgrind обнаружил утечку памяти

user@netbook:~/Учёба/C/Список$ valgrind --leak-check=full ./test > /dev/null
==15436== Memcheck, a memory error detector
==15436== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==15436== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info
==15436== Command: ./test
==15436== 
==15436== 
==15436== HEAP SUMMARY:
==15436==     in use at exit: 104 bytes in 1 blocks
==15436==   total heap usage: 11 allocs, 10 frees, 1,144 bytes allocated
==15436== 
==15436== 104 bytes in 1 blocks are definitely lost in loss record 1 of 1
==15436==    at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==15436==    by 0x4011B9: lst_insert_before (list.c:103)
==15436==    by 0x4008D7: main (test.c:52)
==15436== 
==15436== LEAK SUMMARY:
==15436==    definitely lost: 104 bytes in 1 blocks
==15436==    indirectly lost: 0 bytes in 0 blocks
==15436==      possibly lost: 0 bytes in 0 blocks
==15436==    still reachable: 0 bytes in 0 blocks
==15436==         suppressed: 0 bytes in 0 blocks
==15436== 
==15436== For counts of detected and suppressed errors, rerun with: -v
==15436== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
@mymedia2 mymedia2 added the bug label Apr 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant