memcheck - Understanding Valgrind o/p -


i running memcheck using valgrind. o/p

==3091== 204 bytes in 17 blocks lost in loss record 1,406 of 2,299 

what mean ?

what guess there 204 bytes memory loss

but meant

17 blocks ? 

and how know how many time memory leak happened same function ?

complete stack trace of valgrind

==3091== 204 bytes in 17 blocks lost in loss record 1,406 of 2,299 ==3091==    @ 0x4a05e1c: malloc (vg_replace_malloc.c:195) ==3091==    0x4ca304: fs_get (fs_unix.c:38) ==3091==    0x4e58c1: cpystr (misc.c:74) ==3091==    0x4d130f: ip_nametoaddr (ip_unix.c:178) ==3091==    0x4d15f4: tcp_open (tcp_unix.c:192) ==3091==    0x4d41a5: cc_connect_http_proxy (proxy.c:164) ==3091==    0x4d4b0c: cc_connect (proxy.c:571) ==3091==    0x4d506d: ssl_open (osdep.c:353) ==3091==    0x4e56c3: net_open_work (mail.c:6240) ==3091==    0x4e558a: net_open (mail.c:6196) ==3091==    0x4fba04: imap_open (imap4r1.c:841) ==3091==    0x4d9cb1: mail_open_work (mail.c:1355) 

it means there 17 different calls malloc (or allocator function) return not free'd. 17 allocations represented total of 204 bytes being lost.


Comments

Popular posts from this blog

linux - Using a Cron Job to check if my mod_wsgi / apache server is running and restart -

actionscript 3 - TweenLite does not work with object -

jQuery Ajax Render Fragments OR Whole Page -