On 02/22/2014 09:00 PM, Nehal J Wani wrote:
While running virscsitest, it was found that valgrind pointed out the
following
memory leak:
==320== 5 bytes in 1 blocks are definitely lost in loss record 4 of 37
==320==at 0x4A069EE: malloc (vg_replace_malloc.c:270)
==320==by
While running virscsitest, it was found that valgrind pointed out the following
memory leak:
==320== 5 bytes in 1 blocks are definitely lost in loss record 4 of 37
==320==at 0x4A069EE: malloc (vg_replace_malloc.c:270)
==320==by 0x3E6CE81171: strdup (strdup.c:43)
==320==by 0x4CB28DF:
